infomaniak_unlock_drive_user
Unlock a kDrive user through POST /2/drive/{drive_id}/users/{user_id}/unlock. Two-phase commit with current user guard.
This record as markdown: /tools/henrikogaard-infomaniak-admin-mcp/infomaniak-unlock-drive-user.md
What infomaniak_unlock_drive_user does on Infomaniak Admin
AI agents use infomaniak_unlock_drive_user 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_unlock_drive_user is rated Medium
This tool modifies user state reversibly (unlock is reversible via lock). It affects account access and permissions but does not delete data or move money. The POST method and unlock semantics classify it as Write rather than Execute. Severity is high because unlocking a user account could grant unauthorized access if misused, and the blast radius includes account compromise.
From the tool's definition Unlock a kDrive user through POST /2/drive/{drive_id}/users/{user_id}/unlock. POST method indicates a write/mutation operation that modifies user account state by changing lock status.
Attacks that exploit this kind of access
The rule that runs infomaniak_unlock_drive_user 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_unlock_drive_user, this is the rule to start with:
infomaniak_unlock_drive_user 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_unlock_drive_user call is checked against it from then on.
Questions about infomaniak_unlock_drive_user
Unlock a kDrive user through POST /2/drive/{drive_id}/users/{user_id}/unlock. Two-phase commit with current user 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_unlock_drive_user: 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_unlock_drive_user 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_unlock_drive_user 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_unlock_drive_user. 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_unlock_drive_user 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