AI agents call get-recycle-bin-document-root to retrieve information from Mcp Dev without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves information about the document recycle bin root items without modifying, deleting, or executing any operations. It is a simple data retrieval operation with no side effects. Severity is low because access to recycle bin metadata poses minimal risk even if misused by an agent.
From the tool's definition Tool name 'get-recycle-bin-document-root' and description 'Gets root items for the document recycle bin' indicate a retrieval operation. The verb 'Gets' and the context of retrieving recycle bin root items are consistent with read-only data retrieval.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
Gets root items for the document recycle bin. It is categorised as a Read tool in the Mcp Dev MCP Server, which means it retrieves data without modifying state.
Register the Mcp Dev MCP server in PolicyLayer and add a rule for get-recycle-bin-document-root: 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.
get-recycle-bin-document-root is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get-recycle-bin-document-root 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 get-recycle-bin-document-root. 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.
get-recycle-bin-document-root 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 →