infomaniak_remove_drive_trash_item
Permanently remove one file or folder from kDrive trash. Destructive two-phase commit with trashed-item guard; not undoable.
This record as markdown: /tools/henrikogaard-infomaniak-admin-mcp/infomaniak-remove-drive-trash-item.md
What infomaniak_remove_drive_trash_item does on Infomaniak Admin
AI agents call infomaniak_remove_drive_trash_item to permanently remove resources in Infomaniak Admin, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why infomaniak_remove_drive_trash_item is rated Critical
This tool permanently deletes data from trash with no undo capability, fitting the Destructive category definition. While it operates on already-trashed items (reducing blast radius compared to direct deletion), permanent removal of user files is a high-severity operation. The two-phase commit provides some protection against accidental misuse, but the action itself cannot be reversed once committed.
From the tool's definition Tool description explicitly states 'Permanently remove one file or folder from kDrive trash' and 'not undoable.' The name contains 'remove' and description confirms irreversible deletion.
Attacks that exploit this kind of access
The rule that runs infomaniak_remove_drive_trash_item safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Infomaniak Admin, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For infomaniak_remove_drive_trash_item, this is the rule to start with:
infomaniak_remove_drive_trash_item 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 Infomaniak Admin, apply this rule, and every infomaniak_remove_drive_trash_item call is checked against it from then on.
Questions about infomaniak_remove_drive_trash_item
Permanently remove one file or folder from kDrive trash. Destructive two-phase commit with trashed-item guard; not undoable. It is categorised as a Destructive tool in the Infomaniak Admin MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Infomaniak Admin MCP server in PolicyLayer and add a rule for infomaniak_remove_drive_trash_item: 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 Infomaniak Admin. Nothing to install.
infomaniak_remove_drive_trash_item 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 infomaniak_remove_drive_trash_item 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 infomaniak_remove_drive_trash_item. 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.
infomaniak_remove_drive_trash_item is provided by the Infomaniak Admin MCP server (henrikogaard/infomaniak-admin-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Infomaniak Admin, and thousands of servers like it.
Across the catalogue