Governed ability
Delete post meta
aafm/delete-post-metaGuarded write
Delete post meta is a governed ability in Agent Abilities for MCP, a free WordPress plugin that runs an MCP server on your site.
Delete an allowlisted meta key from a post the agent can edit. Removes all values of that key. The response returns the old value when it is plain text or a number. Keys are opt-in: an administrator exposes each one under Exposed meta keys in the Content sub-tab of the Abilities tab.
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 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 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 and the identifiers it touched, never free-text content.
- It can delete
This ability deletes permanently. What it removes cannot be restored from the Trash. While change history is on, the Changes tab can put a deleted custom field back, unless the key looks like a secret. The last administrator can never be removed.
Delete post meta 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.
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?
Delete post meta removes every value stored under that meta key on the post. Only allowlisted keys can be targeted.
Is there a safety net?
Delete post meta removes the value, and WordPress has no per-field Trash for meta. While change history is on, the Changes tab keeps the earlier value for up to 30 days and can put it back if the post has not been edited since, unless the key looks like a secret. The ability stays off until enabled, needs edit access to the post, and is audited.
Why can it not touch image alt text or the featured image?
Alt text lives under `_wp_attachment_image_alt` and the featured image under `_thumbnail_id`. Both are protected meta in stock WordPress and are refused for every caller whatever their role. Clear alt text through update media, and the thumbnail through set featured image or the post's featured_media field. Since 1.7.0 the refusal names the right tool instead of reading as a permission problem.
Can I undo it?
Yes, while change history is on. The Changes tab reverts it if the item has not been edited since, and keeps changes for up to 30 days. It puts back the earlier value of the custom field, for the keys the plugin lets an agent write. A key whose name looks like a secret, such as a password, token or API key, has no value stored, so that change cannot be reverted. An agent can also revert it with Undo change from its own connection within 24 hours, once you switch Undo change on and while this tool stays on for that connection.
Delete post meta is one of the 25 tools the Changes tab records. Undo what an AI agent changed lists them all, and what cannot be undone.
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.