infomaniak_restore_drive_trash_item
Restore one file or folder from kDrive trash. Two-phase commit with trashed-item guard.
This record as markdown: /tools/henrikogaard-infomaniak-admin-mcp/infomaniak-restore-drive-trash-item.md
What infomaniak_restore_drive_trash_item does on Infomaniak Admin
AI agents use infomaniak_restore_drive_trash_item to create or update resources in Infomaniak Admin, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Infomaniak Admin environment.
Why infomaniak_restore_drive_trash_item is rated Medium
This tool restores (recovers) deleted files or folders from trash—a Write operation because it modifies the file system state reversibly. It is not Destructive because restoration is undoable (items can be deleted again). It is not Read because it changes state. The 'two-phase commit with trashed-item guard' adds safety but does not change the fundamental category.
From the tool's definition Tool name 'restore_drive_trash_item' and description 'Restore one file or folder from kDrive trash' indicate a reversible modification operation that recovers previously deleted data.
Attacks that exploit this kind of access
The rule that runs infomaniak_restore_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_restore_drive_trash_item, this is the rule to start with:
infomaniak_restore_drive_trash_item stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Infomaniak Admin, apply this rule, and every infomaniak_restore_drive_trash_item call is checked against it from then on.
Questions about infomaniak_restore_drive_trash_item
Restore one file or folder from kDrive trash. Two-phase commit with trashed-item guard. It is categorised as a Write tool in the Infomaniak Admin MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Infomaniak Admin MCP server in PolicyLayer and add a rule for infomaniak_restore_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_restore_drive_trash_item is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the infomaniak_restore_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_restore_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_restore_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.
This server
Across the catalogue