delete-element-folder-from-recycle-bin
Permanently deletes an element folder from the recycle bin by Id
This record as markdown: /tools/mcp-dev/delete-element-folder-from-recycle-bin.md
What delete-element-folder-from-recycle-bin does on Mcp Dev
AI agents call delete-element-folder-from-recycle-bin 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.
Why delete-element-folder-from-recycle-bin is rated Critical
This tool irreversibly deletes data (element folder) from the recycle bin. Once permanently deleted, the folder and its contents cannot be recovered. This is a classic Destructive action that exceeds Execute category since it specifically involves permanent, unrecoverable deletion.
From the tool's definition The tool "permanently deletes an element folder from the recycle bin" - the word "permanently" indicates irreversible data destruction. This is a Destructive operation as it cannot be undone.
Attacks that exploit this kind of access
The rule that runs delete-element-folder-from-recycle-bin 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-folder-from-recycle-bin, this is the rule to start with:
delete-element-folder-from-recycle-bin is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Dev, apply this rule, and every delete-element-folder-from-recycle-bin call is checked against it from then on.
Questions about delete-element-folder-from-recycle-bin
Permanently deletes an element folder from the recycle bin 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-from-recycle-bin: 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-from-recycle-bin 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-from-recycle-bin 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-from-recycle-bin. 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-from-recycle-bin 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.
Across the catalogue