Move a file or folder to the Trash (reversible delete). Path must be under home directory.
AI agents call files.trash to permanently remove resources in Orchard — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Although technically reversible via Trash recovery, this tool irreversibly removes files from their current location and active filesystem state. The blast radius is high: an AI agent could delete user files, documents, photos, or critical system files under the home directory.
From the tool's definition "Move a file or folder to the Trash" - while the description notes this is "reversible", the tool performs deletion operations on files and folders. The function signature indicates it removes data from the active filesystem.
Documented attack patterns abuse exactly the kind of access files.trash gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Orchard, and nothing reaches the server without passing your rules. This is the rule we recommend for files.trash:
{
"version": "1",
"default": "deny",
"hide": [
"files.trash"
]
}files.trash disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Move a file or folder to the Trash (reversible delete). Path must be under home directory. It is categorised as a Destructive tool in the Orchard MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Orchard MCP server in PolicyLayer and add a rule for files.trash: 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 Orchard. Nothing to install.
files.trash 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 files.trash 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 files.trash. 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.
files.trash is provided by the Orchard MCP server (l22-io/orchard-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Orchard, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
65 Orchard tools catalogued and risk-classified — across an index of 43,000+ MCP servers.