Governed ability
Undo change
aafm/undo-changeGuarded write
Undo change is a governed ability in Agent Abilities for MCP, a free WordPress plugin that runs an MCP server on your site.
Reverts one change this connection made in the last 24 hours, by the id list-changes gave. It puts back the earlier value of the fields that change touched, only if nothing else has edited them since, and it checks again that this connection may still make that edit. Undoing a create moves the item to the Trash. An undo cannot itself be undone from here, and notifications, webhooks and anything already read are not recalled. One change per call, 30 calls an hour. Off by default.
How it is governed
The same model as every ability in the plugin, stated for this one.
- Off until you enable it
Like every ability, Undo change ships switched off. You turn it on one at a time, and an update never switches on a tool it serves.
- Guarded write
Writes stay conservative, and the plugin re-checks the capability before the call runs.
- Capability gated
A connection only sees Undo change if the user you connected can run it, and the plugin checks that capability again before it executes.
- Every call audited
The call is written to the log in your own database, denials included, with the argument keys and the identifiers it touched, never free-text content.
- It overwrites fields
This ability puts earlier values back over the current ones, so it is marked destructive. It reverts only changes this connection made in the last 24 hours, and undoing a create moves the item to the Trash.
Undo change is one of the 30 governed Content abilities. Browse the other Content abilities in the catalog.
See it in action
An illustrative run. Your real calls and data stay on your own site.
Try it with a prompt
Example requests you could paste to your agent.
Undo change 4817, the title edit you just made to post 142.
That last edit was wrong. Revert it.
Put back what you changed on page 12 earlier today, one change at a time.
These are illustrative example prompts. The agent runs them as the user you connected, checked against that user's capabilities and written to your audit log.
Frequently asked
Short answers for Undo change.
What can an agent undo?
Only changes its own connection made in the last 24 hours, by the id list-changes gave, and only if nothing else has edited those fields since. It also checks again that the connection may still make that edit. Undoing a create moves the item to the Trash.
Is there a limit?
One change per call and 30 calls an hour per connection. A change that is older, was made by another connection, or touched a tool outside the 25 the Changes tab covers has to be reverted by the site owner, or cannot be undone at all.
Can an undo be undone?
Not by an agent. The undo is recorded as a change of its own that only the site owner can revert from the Changes tab. Notifications, webhooks and anything already read are not recalled.
Is it on by default?
No. Undo change is destructive, so it starts off, and the Read only, Content editor and Shop manager presets leave it out. An administrator enables it in the Abilities tab.
Governed by default, from the first call.
Undo change is off until you enable it, scoped to the user you connect, and logged like everything else. Turn on only what you need.
Every ability off until you enable it, capability-gated on every call.