revision_delete
Löscht eine spezifische Revision
This record as markdown: /tools/c-sakel-wp-mcp-server/revision-delete.md
What revision_delete does on WordPress MCP Server
AI agents call revision_delete 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 revision_delete is rated Critical
This tool permanently removes revision history, which cannot be undone. Revision deletion is a destructive operation that eliminates historical versions of content. While not as critical as deleting live content, it removes audit trails and recovery options, warranting 'high' severity due to potential data loss and compliance implications in a WordPress environment where revision history can be important for content…
From the tool's definition Tool name 'revision_delete' combined with description 'Löscht eine spezifische Revision' (German: 'Deletes a specific revision') explicitly indicates irreversible deletion of WordPress post/page revisions.
Attacks that exploit this kind of access
The rule that runs revision_delete 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 revision_delete, this is the rule to start with:
revision_delete 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 revision_delete call is checked against it from then on.
Questions about revision_delete
Löscht eine spezifische Revision. 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 revision_delete: 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.
revision_delete 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 revision_delete 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 revision_delete. 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.
revision_delete 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