An agent can check whether a specific comment looks like spam and pull the site's antispam performance statistics.
2 read
View abilitiesDisable Comments abilities, governed through the Bridge
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.
- Abilities
- 31 read1 write1 destructive
- Active installs
- 1M+
- Rating
- 94% (281 ratings)
- Version
- 2.9.0
- Requires
- WP 5.0+, PHP 7.0+
- Last updated
- 2026-09-01 9:35am GMT
View Disable Comments on WordPress.org
What has to be true first
Disable Comments needs WordPress 6.9 or later and the plugin active. Reading or changing where comments are disabled requires manage_options (manage_network_plugins on a multisite network with sitewide settings on), and deleting comments requires the same capability.
A note on the count below
easymcp's listing counted only the read-only status ability; the source also registers a settings-write ability and a comment-delete ability.
The 3 Disable Comments abilities
Grouped by what each one can change. Every one starts off until you enable it.
Read 1
- Read
Get comment status
Reports where comments are currently disabled: site-wide, per post type, or across a multisite network.
Write 1
- Write
Set comment status
Turns comments off everywhere or replaces the list of post types with comments disabled.
Destructive 1
- Destructive
Delete comments
Permanently deletes comments matching a mode such as everywhere, a post type, a comment type, or spam only.
How to switch these on
Four steps from two active plugins to a governed connection.
Install Disable Comments and Agent Abilities for MCP
Both plugins need to be active on the same WordPress site. Disable Comments 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 Disable Comments 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 Disable Comments work with the Bridge?
Yes. All three abilities register unconditionally whenever the plugin is active and the Abilities API is present, so the Bridge discovers the read, write and delete abilities as soon as an operator switches each one on.
Do Disable Comments's abilities register automatically?
Yes, unconditionally, once Disable Comments is active. Nothing else has to be configured for the Bridge to discover them.
Does Disable Comments need anything special to work with the Bridge?
Disable Comments needs WordPress 6.9 or later and the plugin active. Reading or changing where comments are disabled requires manage_options (manage_network_plugins on a multisite network with sitewide settings on), and deleting comments requires the same capability.
More Security & privacy plugins
An 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 abilitiesAn 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.
3 read3 write
View abilitiesVerified from Disable Comments'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, WPDeveloper or Disable Comments. Back to the full directory.
Bridge Disable Comments, 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.