wordpress_delete_post
AI agents call wordpress_delete_post to permanently remove resources in WordPress MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting a WordPress post removes content permanently and cannot be reversed without restoration from backups. This is a destructive operation with significant blast radius if executed unintentionally or maliciously by an AI agent. Confidence is high despite empty description because the tool name itself clearly indicates destructive intent.
From the tool's definition Tool name 'wordpress_delete_post' indicates irreversible deletion of post data. The 'delete' verb combined with 'post' (a core WordPress content object) matches the Destructive category definition: 'irreversibly deletes or overwrites data, or actions that…
Attacks that exploit this kind of access
wordpress_delete_post. It is categorised as a Destructive tool in the WordPress MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the WordPress MCP Server MCP server in PolicyLayer and add a rule for wordpress_delete_post: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches WordPress MCP Server. Nothing to install.
wordpress_delete_post is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the wordpress_delete_post rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for wordpress_delete_post. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
wordpress_delete_post is provided by the WordPress MCP Server MCP server (tonypepperwidow123-blip/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
wordpress_delete_post is one line of WordPress MCP Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →