update-document-version-prevent-cleanup
Prevent cleanup for a specific document version
This record as markdown: /tools/mcp-dev/update-document-version-prevent-cleanup.md
What update-document-version-prevent-cleanup does on Mcp Dev
AI agents use update-document-version-prevent-cleanup 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 update-document-version-prevent-cleanup is rated Medium
This tool modifies document version cleanup settings, which constitutes a Write operation. The change is reversible and affects metadata/configuration rather than core data deletion. Severity is medium because interfering with cleanup prevention could affect document storage management and system maintenance workflows, though the immediate blast radius is limited to a single document version's lifecycle state.
From the tool's definition Tool description states it 'Prevent cleanup for a specific document version', indicating modification of document version management state. The action is reversible (cleanup prevention can be toggled off), and does not delete data or execute arbitrary code.
Attacks that exploit this kind of access
The rule that runs update-document-version-prevent-cleanup 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 update-document-version-prevent-cleanup, this is the rule to start with:
update-document-version-prevent-cleanup 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 update-document-version-prevent-cleanup call is checked against it from then on.
Questions about update-document-version-prevent-cleanup
Prevent cleanup for a specific document 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 update-document-version-prevent-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 Mcp Dev. Nothing to install.
update-document-version-prevent-cleanup 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 update-document-version-prevent-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.
Set action: deny in the PolicyLayer policy for update-document-version-prevent-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.
update-document-version-prevent-cleanup 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