An agent can check whether a specific comment looks like spam and pull the site's antispam performance statistics.
2 read
View abilitiesActiveLayer Anti-Spam abilities, governed through the Bridge
An AI agent can list and search the spam-filter's flagged form and comment submissions, pull one submission's detail, read aggregated spam statistics, and read the plugin's non-sensitive settings.
- Abilities
- 55 read
- Active installs
- 9K+
- Rating
- 98% (8 ratings)
- Version
- 1.7.1
- Requires
- WP 5.5+, PHP 7.2+
- Last updated
- 2026-09-15 5:32am GMT
View ActiveLayer Anti-Spam on WordPress.org
What has to be true first
ActiveLayer Anti-Spam needs to be installed and active on WordPress 6.9 or later for its abilities to register. All five abilities share one permission check tied to a custom manage_activelayer capability, so whichever role holds that capability gets read access to submissions, search, statistics and settings alike, there is no separate split by ability.
The 5 ActiveLayer Anti-Spam abilities
Grouped by what each one can change. Every one starts off until you enable it.
Read 5
- Read
List submissions
Lists spam-filter submissions logged for forms and comments.
- Read
Search submissions
Searches logged submissions by query terms.
- Read
Get submission
Returns the detail of one logged submission.
- Read
Get statistics
Returns aggregated spam-blocking statistics.
- Read
Get settings
Returns the plugin's non-sensitive settings.
How to switch these on
Four steps from two active plugins to a governed connection.
Install ActiveLayer Anti-Spam and Agent Abilities for MCP
Both plugins need to be active on the same WordPress site. ActiveLayer Anti-Spam 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 ActiveLayer Anti-Spam 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 ActiveLayer Anti-Spam work with the Bridge?
Yes. The plugin registers five abilities with wp_register_ability under its own namespace and none of them opt out of the Bridge's discovery, so every one can be switched on once the site operator enables it.
Do ActiveLayer Anti-Spam's abilities register automatically?
Yes, unconditionally, once ActiveLayer Anti-Spam is active. Nothing else has to be configured for the Bridge to discover them.
Does ActiveLayer Anti-Spam need anything special to work with the Bridge?
ActiveLayer Anti-Spam needs to be installed and active on WordPress 6.9 or later for its abilities to register. All five abilities share one permission check tied to a custom manage_activelayer capability, so whichever role holds that capability gets read access to submissions, search, statistics and settings alike, there is no separate split by ability.
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 ActiveLayer Anti-Spam'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, Syed Balkhi or ActiveLayer Anti-Spam. Back to the full directory.
Bridge ActiveLayer Anti-Spam, 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.