An agent can check whether a specific comment looks like spam and pull the site's antispam performance statistics.
2 read
View abilitiesCookiebot abilities, governed through the Bridge
An agent can read the plugin's configuration status, verify the setup against Cookiebot's own checklist, read a compliance summary, set the Domain Group ID, toggle Google Consent Mode v2, and install and activate the Privacy Policy Generator plugin.
- Abilities
- 63 read3 write
- Active installs
- 100K+
- Rating
- 88% (440 ratings)
- Version
- 4.7.3
- Requires
- WP 4.4+, PHP 5.6+
- Last updated
- 2026-09-14 11:57am GMT
View Cookiebot on WordPress.org
What has to be true first
Cookiebot must be active with WordPress 6.9 or newer. Every ability checks the manage_options capability, and install-ppg additionally requires install_plugins.
The 6 Cookiebot abilities
Grouped by what each one can change. Every one starts off until you enable it.
Read 3
- Read
Get Cookiebot Status
Returns the current Cookiebot configuration: Domain Group ID presence, GCM status, blocking mode, banner state, and plugin version.
- Read
Verify Cookiebot Setup
Checks the Domain Group ID, Google Consent Mode v2, and blocking mode against Cookiebot's recommended configuration.
- Read
Get Compliance Summary
Returns the privacy regulations covered, scan status, and detected plan type.
Write 3
- Write
Set Domain Group ID
Sets the Cookiebot or Usercentrics Domain Group ID.
- Write
Toggle Google Consent Mode v2
Enables or disables Google Consent Mode v2.
- Write
Install Privacy Policy Generator
Installs and activates the Privacy Policy Generator plugin.
How to switch these on
Four steps from two active plugins to a governed connection.
Install Cookiebot and Agent Abilities for MCP
Both plugins need to be active on the same WordPress site. Cookiebot registers its own abilities; this plugin discovers and governs them.
Open the Other plugins screen
In Agent Abilities for MCP, open the Bridge tab (labeled "Other plugins" in the admin). Abilities from every registered plugin appear there, grouped by the plugin that registered them.
Enable one ability at a time
Every ability from Cookiebot starts off. Turn on only the ones you want an agent to reach, or enable the whole set in one click.
Connect as a least-privilege user
Approve the connection as a WordPress account scoped to what you actually want the agent to do. Each call still re-checks that account’s capability before it runs.
Read more in how bridging works or the full documentation.
Frequently asked questions
Does Cookiebot work with the Bridge?
Yes. It registers six abilities through wp_register_ability unconditionally, covering status, compliance, and configuration of the Cookiebot consent banner.
Do Cookiebot's abilities register automatically?
Yes, unconditionally, once Cookiebot is active. Nothing else has to be configured for the Bridge to discover them.
Does Cookiebot need anything special to work with the Bridge?
Cookiebot must be active with WordPress 6.9 or newer. Every ability checks the manage_options capability, and install-ppg additionally requires install_plugins.
More Security & privacy plugins
An agent can check exactly where comments are currently disabled across the site or a multisite network, turn comments off or on for specific post types, and delete existing comments.
1 read1 write1 destructive
View abilitiesAn agent can search and read the WordPress activity log: recent events, a single event's detail, one user's activity, failed login attempts, and a statistics summary grouped by users, content, media, plugins, core and notes, all without being able to change anything.
6 read
View abilitiesVerified from Cookiebot's own free wordpress.org code on 28 September 2026, not from its marketing claims. Not every ability listed here has been run end to end against a live site. Plugin authors change their code, so a name, a capability, or a condition can be different in a later release. This site is not affiliated with, or endorsed by, cookiebot or Cookiebot. Back to the full directory.
Bridge Cookiebot, keep the same control.
Every ability starts off, is scoped to the user you connect, and is written to the same audit log as core. Turn on only what you need.
Off by default. Capability checked on every call.