legal_restore_generator
Restore a generated document to how it was before the generator first wrote it, and stop generating it. Requires cvrt-legal 0.7.0+.
This record as markdown: /tools/io-github-cvrt-jh-wordpress-mcp/legal-restore-generator.md
What legal_restore_generator does on Wordpress
AI agents call legal_restore_generator to permanently remove resources in Wordpress, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why legal_restore_generator is rated Critical
Irreversibly reverts document state and halts generation, undoing prior changes permanently.
From the tool's definition Restore a generated document to how it was before... stop generating
Attacks that exploit this kind of access
The rule that runs legal_restore_generator safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Wordpress, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For legal_restore_generator, this is the rule to start with:
legal_restore_generator 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, apply this rule, and every legal_restore_generator call is checked against it from then on.
Questions about legal_restore_generator
Restore a generated document to how it was before the generator first wrote it, and stop generating it. Requires cvrt-legal 0.7.0+. It is categorised as a Destructive tool in the Wordpress MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Wordpress MCP server in PolicyLayer and add a rule for legal_restore_generator: 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. Nothing to install.
legal_restore_generator 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 legal_restore_generator 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 legal_restore_generator. 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.
legal_restore_generator is provided by the Wordpress MCP server (@cavort-it-systems/wordpress-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Wordpress, and thousands of servers like it.
Across the catalogue