How to find what an AI agent did on your WordPress site
Use the Activity Log in Agent Abilities for MCP to find what an AI agent did: filter by connection, tool and date, read denied rows, and export a CSV.
Read moreWhat 1.9.0 adds: a searchable Activity Log and alerts
1.9.0 makes the Activity Log searchable, records why a call was refused, and adds optional email alerts that stay off until you enable them.
Read moreWhat 1.7.8 changes: bridged tools now show up in the tool list
37 bridged tools from eight plugins worked when called but never appeared in the tool list. 1.7.8 lists them, names the source in errors, and fixes three bugs.
Read moreWhat 1.7.7 changes: one Save changes button on the Abilities tab
The Abilities tab had a main Save button plus four on its cards, and pressing only the main one lost edits to meta keys and content types. 1.7.7 has one button.
Read moreWhat 1.7.6 changes: an OAuth token now works on the MCP route only
Before 1.7.6, an OAuth token for the MCP endpoint also signed its holder in elsewhere on a WordPress site. What it reached, what changed, and what else shipped.
Read moreWhat we fixed: a switch that would not turn off
On sites with a persistent object cache, read-only mode and the high-risk lock could refuse to change, and the activity log recorded the change as done anyway.
Read moreWhat 1.7.2 adds: a consent screen that shows who is asking
The sign-in screen now identifies a connector by its verified redirect host, and the Activity Log records requests that reach WordPress and fail.
Read moreYour agent signs in, then nothing happens
A completed sign-in with no tool calls after it usually means a CDN or firewall blocked the request. Read that in the Activity Log, confirm it, and fix it.
Read moreWhat we fixed in the 1.7.1 correctness release
A fix-only release: WPML sweeps now read every configured language, tool discovery matches permission, and a broken discovery route resolves again.
Read moreWhat 1.7.0 adds: Enable all writes, and a fuller audit log
Version 1.7.0 adds a one-click way to enable a section's ordinary writes, deliberately leaving deletes and high-risk abilities locked, plus a fuller audit log.
Read moreA WordPress AI audit log you can trust
Three 1.6.2 fixes make the plugin's audit log worth trusting: it records the true cause of a block, covers every path that changes state, and stays readable.
Read moreWe said the audit log stored nothing. That was not quite true.
In 1.6.2 we corrected a claim about the audit log. It keeps identifier-only values by design, never free-text content, and here is why that line matters.
Read moreWhat we fixed in the 1.6.2 hardening release
Version 1.6.2 corrects a claim about our own audit log, tightens who can edit customer data, and closes gaps in what the plugin records and sanitizes.
Read more