Move a media item to the recycle bin
AI agents call move-media-to-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.
Moving media to the recycle bin is effectively a delete operation. While it may be recoverable in some CMS implementations, it removes the media from active availability and is typically considered irreversible in automated/agent workflows. The blast radius is high as media items may be referenced across many pages and content items, causing broken references site-wide.
From the tool's definition 'Move a media item to the recycle bin' — moving to recycle bin is a soft-delete operation that removes the item from active use
Attacks that exploit this kind of access
Move a media item to the recycle bin. 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 move-media-to-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.
move-media-to-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 move-media-to-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 move-media-to-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.
move-media-to-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.
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 →