create-document-version-rollback
Rollback document to a specific version
This record as markdown: /tools/mcp-dev/create-document-version-rollback.md
What create-document-version-rollback does on Mcp Dev
AI agents call create-document-version-rollback to permanently remove resources in Mcp Dev, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why create-document-version-rollback is rated Critical
A rollback operation replaces the current content with a historical snapshot, effectively destroying all edits made after that version. While the older version is restored (making it not a pure delete), the current state is irreversibly overwritten and cannot be recovered without another rollback or backup. This qualifies as Destructive due to the irreversible loss of the current document state.
From the tool's definition 'Rollback document to a specific version' — rolling back overwrites the current version of a document with an older state, irreversibly discarding any changes made since that version
Attacks that exploit this kind of access
The rule that runs create-document-version-rollback safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Dev, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create-document-version-rollback, this is the rule to start with:
create-document-version-rollback 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 Mcp Dev, apply this rule, and every create-document-version-rollback call is checked against it from then on.
Questions about create-document-version-rollback
Rollback document to a specific version. It is categorised as a Destructive tool in the Mcp Dev MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Mcp Dev MCP server in PolicyLayer and add a rule for create-document-version-rollback: 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 Mcp Dev. Nothing to install.
create-document-version-rollback 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 create-document-version-rollback 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 create-document-version-rollback. 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.
create-document-version-rollback is provided by the Mcp Dev MCP server (@umbraco-cms/mcp-dev). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Dev, and thousands of servers like it.
Across the catalogue