Governed ability
Delete post meta
aafm/delete-post-meta Guarded write
Delete an allowlisted meta key from a post the agent can edit. Removes all values of that key.
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 meta 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 meta 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.
Remove the old promo_banner meta key from post 142.
Delete the deprecated subtitle_v1 custom field on that page.
Clear the seasonal_tag meta off post 305.
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 meta.
What exactly gets removed?
Every value stored under that meta key on the post. Only allowlisted keys can be targeted.
Is there a safety net?
There is no per-field Trash for meta, so this is a hard delete. It stays off until enabled, needs edit access to the post, and is audited.
Governed by default, from the first call.
Delete post meta 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.