An agent can check whether a specific comment looks like spam and pull the site's antispam performance statistics.
SudoWP Radar abilities, governed through the Bridge
An agent can trigger a full security audit of every registered WordPress ability on the site and get back a structured findings report with a severity breakdown and a recommended action. It does not change anything on the site, it only scans and reports.
- Abilities
- 11 destructive
- Active installs
- Fewer than 10
- Rating
- No ratings yet
- Version
- 1.3.0
- Requires
- WP 6.9+, PHP 8.1+
- Last updated
- 2026-07-12 9:59pm GMT
View SudoWP Radar on WordPress.org
What has to be true first
Needs WordPress 6.9 or newer and PHP 8.1 or newer, with SudoWP Radar active. The single ability checks a plugin-defined custom capability rather than a standard WordPress one, and the same user is rate-limited to one audit every 30 seconds.
A note on the count below
The single ability has no readonly or destructive annotation in its meta at all (only show_in_rest is set), so per the Bridge's fail-safe rule it is bridged as destructive even though the audit itself only reads and reports, never writes.
The 1 SudoWP Radar ability
Grouped by what each one can change. Every one starts off until you enable it.
Destructive 1
- Destructive
Run Security Radar Scan
Audits every registered WordPress ability for security misconfigurations and returns a structured findings report.
How to switch these on
Four steps from two active plugins to a governed connection.
Install SudoWP Radar and Agent Abilities for MCP
Both plugins need to be active on the same WordPress site. SudoWP Radar 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 SudoWP Radar 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 SudoWP Radar work with the Bridge?
Yes. It registers one ability, sudowp-radar/audit, in the core Abilities API. The ability sets meta.show_in_rest to false to keep it out of the REST Abilities endpoint, but that does not remove it from the registry the Bridge reads directly, so it is still discoverable.
Do SudoWP Radar's abilities register automatically?
Yes, unconditionally, once SudoWP Radar is active. Nothing else has to be configured for the Bridge to discover them.
Does SudoWP Radar need anything special to work with the Bridge?
Needs WordPress 6.9 or newer and PHP 8.1 or newer, with SudoWP Radar active. The single ability checks a plugin-defined custom capability rather than a standard WordPress one, and the same user is rate-limited to one audit every 30 seconds.
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.
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.
Verified from SudoWP Radar'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, sudowp or SudoWP Radar. Back to the full directory.
Bridge SudoWP Radar, 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.