wp_delete_post
Löscht einen WordPress-Beitrag (verschiebt in Papierkorb oder endgültig)
This record as markdown: /tools/c-sakel-wp-mcp-server/wp-delete-post.md
What wp_delete_post does on WordPress MCP Server
AI agents call wp_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.
Why wp_delete_post is rated Critical
This tool can permanently delete WordPress posts without recovery, which is irreversible data loss. Even though it offers a soft-delete option (trash), the capability to permanently delete content ('endgültig') classifies it as Destructive rather than Write. An AI agent misusing this tool could permanently erase published content, causing significant damage.
From the tool's definition Tool name 'wp_delete_post' and description states 'Löscht einen WordPress-Beitrag (verschiebt in Papierkorb oder endgültig)' — explicitly deletes a WordPress post, either to trash or permanently ('endgültig').
Attacks that exploit this kind of access
The rule that runs wp_delete_post safely
PolicyLayer is an MCP gateway: it sits between your AI agents and WordPress MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For wp_delete_post, this is the rule to start with:
wp_delete_post is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect WordPress MCP Server, apply this rule, and every wp_delete_post call is checked against it from then on.
Questions about wp_delete_post
Löscht einen WordPress-Beitrag (verschiebt in Papierkorb oder endgültig). 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 wp_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.
wp_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 wp_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 wp_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.
wp_delete_post is provided by the WordPress MCP Server MCP server (c-sakel/wp-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on WordPress MCP Server, and thousands of servers like it.
Across the catalogue