An agent can check whether a specific comment looks like spam and pull the site's antispam performance statistics.
2 read
View abilitiesSimple History abilities, governed through the Bridge
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.
- Abilities
- 66 read
- Active installs
- 300K+
- Rating
- 98% (491 ratings)
- Version
- 5.34.0
- Requires
- WP 6.3+, PHP 7.4+
- Last updated
- 2026-09-28 4:38pm GMT
View Simple History on WordPress.org
What has to be true first
Needs WordPress 6.9 or newer with the Abilities API active; Simple History itself only requires WordPress 6.3, so on an older site the abilities silently do not register. Reading events, one event, search, user activity, and failed logins all require the edit_pages capability by default (filterable), while the statistics summary requires manage_options, so a user who can read the log may still be refused there.
- The simple_history/abilities/enabled filter must resolve true (default true), since another plugin or mu-plugin can return false from it to turn off all ability registration
The 6 Simple History abilities
Grouped by what each one can change. Every one starts off until you enable it.
Read 6
- Read
Get Recent Activity Log Events
Returns recent activity log events, newest first, with optional date range, logger, and severity filters.
- Read
Get One Activity Log Event
Returns a single activity log event by its id, including its full context data.
- Read
Search Activity Log Events
Searches the activity log for events whose message text matches a query, newest first.
- Read
Get One User's Activity Log Events
Returns recent activity log events performed by or attributed to one specific user.
- Read
Get Failed Login Attempts
Returns recent failed login attempts, newest first, with repeated attempts collapsed into one row.
- Read
Get Activity Statistics Summary
Returns aggregate event counts for a date range, broken down by users, content, media, plugins, core, and notes.
How to switch these on
Four steps from two active plugins to a governed connection.
Install Simple History and Agent Abilities for MCP
Both plugins need to be active on the same WordPress site. Simple History 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 Simple History 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 Simple History work with the Bridge?
Yes. Simple History registers six abilities through wp_register_ability(), all annotated readonly, so the Bridge discovers them in the core registry and can expose them as safe read-only tools once enabled.
What has to be true for Simple History's abilities to register?
The simple_history/abilities/enabled filter must resolve true (default true), since another plugin or mu-plugin can return false from it to turn off all ability registration.
Does Simple History need anything special to work with the Bridge?
Needs WordPress 6.9 or newer with the Abilities API active; Simple History itself only requires WordPress 6.3, so on an older site the abilities silently do not register. Reading events, one event, search, user activity, and failed logins all require the edit_pages capability by default (filterable), while the statistics summary requires manage_options, so a user who can read the log may still be refused there.
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 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 Simple History'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, Par Thernstrom or Simple History. Back to the full directory.
Bridge Simple History, 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.