delete-element

Deletes an element by Id

SERVERMcp Dev SOURCE@umbraco-cms/mcp-dev

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/mcp-dev/delete-element.md

WHAT IT DOES

What delete-element does on Mcp Dev

AI agents call delete-element 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.

RISK

Why delete-element is rated Critical

This tool permanently removes data from the CMS without possibility of reversal through normal tool operations. While not system-critical in financial impact, deletion of CMS elements can destroy content and configurations. The high confidence reflects clear destructive intent in both name and description.

From the tool's definition Tool name is 'delete-element' with description 'Deletes an element by Id'. The verb 'Deletes' and the irreversible nature of element removal from an Umbraco CMS system indicates destructive action.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

delete-element Hidden

delete-element is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete-element"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about delete-element

What does the delete-element tool do? +

Deletes an element by Id. 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.

How do I enforce a policy on delete-element? +

Register the Mcp Dev MCP server in PolicyLayer and add a rule for delete-element: 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 delete-element? +

delete-element is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete-element? +

Yes. Add a rate_limit block to the delete-element 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 delete-element completely? +

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

delete-element 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 → Critical-risk tools on this server →

Across the catalogue

sms_delete_message on Twilio SMS MCP Server →delete_snapshot on Why Did You Render →calendar_delete_event on Templonix Lite MCP Server →delete_addon_domain on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →