set-element-version-prevent-cleanup

Prevent cleanup for a specific element version

SERVERMcp Dev SOURCE@umbraco-cms/mcp-dev

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/mcp-dev/set-element-version-prevent-cleanup.md

WHAT IT DOES

What set-element-version-prevent-cleanup does on Mcp Dev

AI agents use set-element-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.

RISK

Why set-element-version-prevent-cleanup is rated Medium

This tool modifies configuration or metadata for an element version by setting a cleanup prevention flag. It does not delete data (would be Destructive), execute arbitrary commands (would be Execute), or create new objects (Write is more appropriate than Create since it modifies existing state). The action is reversible—cleanup prevention can be toggled off.

From the tool's definition Tool name contains 'set-' and description states 'Prevent cleanup for a specific element version', indicating modification of element version settings/state.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs set-element-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 set-element-version-prevent-cleanup, this is the rule to start with:

set-element-version-prevent-cleanup Rate-limited

set-element-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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "set-element-version-prevent-cleanup": {
      "limits": [
        {
          "counter": "set-element-version-prevent-cleanup_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Dev, apply this rule, and every set-element-version-prevent-cleanup call is checked against it from then on.

FAQ

Questions about set-element-version-prevent-cleanup

What does the set-element-version-prevent-cleanup tool do? +

Prevent cleanup for a specific element 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.

How do I enforce a policy on set-element-version-prevent-cleanup? +

Register the Mcp Dev MCP server in PolicyLayer and add a rule for set-element-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.

What risk level is set-element-version-prevent-cleanup? +

set-element-version-prevent-cleanup is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit set-element-version-prevent-cleanup? +

Yes. Add a rate_limit block to the set-element-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.

How do I block set-element-version-prevent-cleanup completely? +

Set action: deny in the PolicyLayer policy for set-element-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.

What MCP server provides set-element-version-prevent-cleanup? +

set-element-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.

KEEP EXPLORING

More on Mcp Dev, and thousands of servers like it.

This server

All 419 Mcp Dev tools →

Across the catalogue

emit_assumption_set on 0sec →set-prioity on Kanban MCP Server →team_manager_set_sources on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →