Governed ability
Delete block
aafm/delete-blockGuarded write
Delete block is a governed ability in Agent Abilities for MCP, a free WordPress plugin that runs an MCP server on your site.
Moves a reusable block to the Trash, where you can restore it. Never a permanent delete. Requires delete access to that block.
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, Delete block ships switched off. You turn it on one at a time, and an update never widens access on its own.
- Guarded write
Writes stay conservative, and the plugin re-checks the capability before the call runs.
- Capability gated
A connection only sees Delete block 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 can delete
This ability can delete. Where WordPress supports it, items go to Trash and can be restored, and the last administrator can never be removed.
Delete block is one of the 5 governed Blocks abilities. Browse the other Blocks 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.
Move the old Promo Banner reusable block to the trash.
Trash reusable block 42, I do not need it anymore.
Send synced pattern 108 to the trash so it stops appearing in the inserter.
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 Delete block.
Is this a permanent delete?
No. Delete block moves the reusable block to the Trash, where it can be restored. It is never a permanent delete.
What permission does it need?
Delete block needs delete access to that specific block. The ability is off by default and every call is logged, so a trashed block is both recoverable and traceable.
Governed by default, from the first call.
Delete block 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.