Governed ability
Delete post
aafm/delete-post Guarded write
Permanently delete a post, bypassing the Trash. This cannot be undone - use trash-post to remove a post recoverably instead.
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 post 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 post 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 but never the values.
- 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.
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.
Permanently delete post 501, it cannot be recovered.
Hard delete the spam post with id 88.
Remove post 142 for good, bypassing the Trash.
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 post.
Can I recover it?
No, it bypasses the Trash and cannot be undone. Use trash-post for a recoverable removal.
What prevents misuse?
It is off by default, requires delete access to the post, and is recorded in the audit log.
Governed by default, from the first call.
Delete post 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.