revision_restore
Stellt eine ältere Revision als aktuelle Version wieder her
This record as markdown: /tools/c-sakel-wp-mcp-server/revision-restore.md
What revision_restore does on WordPress MCP Server
AI agents use revision_restore to create or update resources in WordPress MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your WordPress MCP Server environment.
Why revision_restore is rated Medium
While technically reversible (can restore to yet another revision), this tool modifies published content in a significant way and could overwrite recent work or revert important changes. The action is a Write operation because it updates/modifies existing data (content replacement), not a Destructive operation since revisions are retained and the action can be undone by restoring a different revision.
From the tool's definition Tool name 'revision_restore' and description 'Stellt eine ältere Revision als aktuelle Version wieder her' (Restores an older revision as the current version). This overwrites the current content with a previous version.
Attacks that exploit this kind of access
The rule that runs revision_restore 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_restore, this is the rule to start with:
revision_restore stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect WordPress MCP Server, apply this rule, and every revision_restore call is checked against it from then on.
Questions about revision_restore
Stellt eine ältere Revision als aktuelle Version wieder her. It is categorised as a Write tool in the WordPress MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the WordPress MCP Server MCP server in PolicyLayer and add a rule for revision_restore: 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_restore is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the revision_restore 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_restore. 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_restore 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.
This server
Across the catalogue