rollback-element-version
Rollback an element to a specific version
This record as markdown: /tools/mcp-dev/rollback-element-version.md
What rollback-element-version does on Mcp Dev
AI agents use rollback-element-version to create or update resources in Mcp Dev, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Dev environment.
Why rollback-element-version is rated Medium
Rolling back to a previous version is a write/update operation that overwrites current state with a prior version. It is reversible in principle (you can roll back again or re-apply changes), so it falls under Write rather than Destructive. However, it does overwrite the current state, which could cause unintended data loss if misused, warranting a medium severity.
From the tool's definition 'Rollback an element to a specific version' - restores a previous state
Attacks that exploit this kind of access
The rule that runs rollback-element-version 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 rollback-element-version, this is the rule to start with:
rollback-element-version 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 Mcp Dev, apply this rule, and every rollback-element-version call is checked against it from then on.
Questions about rollback-element-version
Rollback an element to a specific version. It is categorised as a Write tool in the Mcp Dev MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Dev MCP server in PolicyLayer and add a rule for rollback-element-version: 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.
rollback-element-version 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 rollback-element-version 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 rollback-element-version. 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.
rollback-element-version 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.
This server
Across the catalogue