Deletes an element folder by Id
AI agents call delete-element-folder 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.
This tool performs a destructive operation that removes an element folder from the Umbraco CMS and cannot be undone. Deletion of a folder may also cascade to child elements, making it a high-severity destructive action. While it targets a specific folder by Id (limiting blast radius somewhat), the permanent nature of deletion and potential cascade effects warrant 'high' severity.
From the tool's definition Tool name: 'delete-element-folder'. Description: 'Deletes an element folder by Id'. The verb 'Deletes' directly indicates irreversible removal of data.
Attacks that exploit this kind of access
Deletes an element folder 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.
Register the Mcp Dev MCP server in PolicyLayer and add a rule for delete-element-folder: 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.
delete-element-folder 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 delete-element-folder 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 delete-element-folder. 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.
delete-element-folder 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →