revision_cleanup

Löscht alte Revisionen und behält nur die letzten N Versionen

SERVERWordPress MCP Server SOURCEc-sakel/wp-mcp-server

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/c-sakel-wp-mcp-server/revision-cleanup.md

WHAT IT DOES

What revision_cleanup does on WordPress MCP Server

AI agents call revision_cleanup 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.

RISK

Why revision_cleanup is rated Critical

The tool explicitly deletes old post revisions from WordPress, which is an irreversible data removal operation. Deleted revisions cannot be recovered, making this Destructive. The blast radius is high because misuse (e.g., keeping only 1 version) could cause permanent loss of content history across many posts.

From the tool's definition 'Löscht alte Revisionen' (deletes old revisions) — irreversibly removes historical revision data, keeping only the last N versions

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs revision_cleanup 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_cleanup, this is the rule to start with:

revision_cleanup Hidden

revision_cleanup is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "revision_cleanup"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect WordPress MCP Server, apply this rule, and every revision_cleanup call is checked against it from then on.

FAQ

Questions about revision_cleanup

What does the revision_cleanup tool do? +

Löscht alte Revisionen und behält nur die letzten N Versionen. 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.

How do I enforce a policy on revision_cleanup? +

Register the WordPress MCP Server MCP server in PolicyLayer and add a rule for revision_cleanup: 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.

What risk level is revision_cleanup? +

revision_cleanup is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit revision_cleanup? +

Yes. Add a rate_limit block to the revision_cleanup 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.

How do I block revision_cleanup completely? +

Set action: deny in the PolicyLayer policy for revision_cleanup. 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.

What MCP server provides revision_cleanup? +

revision_cleanup 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.

KEEP EXPLORING

More on WordPress MCP Server, and thousands of servers like it.

This server

All 192 WordPress MCP Server tools → Critical-risk tools on this server →

Across the catalogue

All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →