This record as markdown: /tools/io-github-heznpc-iconnect/trash-file.md
What trash_file does on Iconnect
AI agents call trash_file to permanently remove resources in Iconnect, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why trash_file is rated Critical
Moving to Trash is a deletion-class operation. Although items can be restored from Trash manually, the action is destructive in intent and effect — it removes the file from its original location and places it in a deletion queue. An AI agent misusing this tool could cause significant data loss. Rated high severity given the blast radius of losing arbitrary files or folders on a macOS system.
From the tool's definition 'trash_file' and 'Move a file or folder to the Trash' — moves files/folders to Trash, which is effectively a deletion operation. While technically recoverable from Trash manually, it removes items from their location and is considered a destructive action.
Attacks that exploit this kind of access
The rule that runs trash_file safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Iconnect, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For trash_file, this is the rule to start with:
trash_file 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 Iconnect, apply this rule, and every trash_file call is checked against it from then on.
Questions about trash_file
Move a file or folder to the Trash using Finder. It is categorised as a Destructive tool in the Iconnect MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Iconnect MCP server in PolicyLayer and add a rule for trash_file: 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 Iconnect. Nothing to install.
trash_file 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 trash_file 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 trash_file. 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.
trash_file is provided by the Iconnect MCP server (iconnect-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Iconnect, and thousands of servers like it.
Across the catalogue