WordPress 게시글을 삭제합니다. force=true이면 휴지통을 건너뛰고 영구 삭제합니다.
AI agents call deletePost 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.
This tool irreversibly deletes data. The description explicitly confirms it can permanently delete posts, bypassing the trash/recycle bin when force=true. This cannot be undone and represents a destructive operation. While the blast radius depends on which posts are targeted, the capability to permanently destroy published content makes this high severity.
From the tool's definition deletePost - deletes WordPress posts; 'force=true이면 휴지통을 건너뛰고 영구 삭제합니다' (if force=true, permanently deletes bypassing trash).
Attacks that exploit this kind of access
WordPress 게시글을 삭제합니다. force=true이면 휴지통을 건너뛰고 영구 삭제합니다. 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 deletePost: 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.
deletePost 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 deletePost 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 deletePost. 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.
deletePost is provided by the WordPress MCP Server MCP server (ssong-openmaru-io/ai-mcp-wordpress). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →