infomaniak_lock_drive_user
Lock a kDrive user through POST /2/drive/{drive_id}/users/{user_id}/lock. Two-phase commit with current user guard.
This record as markdown: /tools/henrikogaard-infomaniak-admin-mcp/infomaniak-lock-drive-user.md
What infomaniak_lock_drive_user does on Infomaniak Admin
AI agents invoke infomaniak_lock_drive_user to trigger actions in Infomaniak Admin. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why infomaniak_lock_drive_user is rated High
This tool locks a user account on kDrive, which triggers an external operation (POST request) that restricts access for the targeted user. Locking a user is a reversible action (the user could be unlocked), so it doesn't qualify as Destructive.
From the tool's definition Lock a kDrive user through POST /2/drive/{drive_id}/users/{user_id}/lock. Two-phase commit with current user guard.
Attacks that exploit this kind of access
The rule that runs infomaniak_lock_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_lock_drive_user, this is the rule to start with:
infomaniak_lock_drive_user stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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_lock_drive_user call is checked against it from then on.
Questions about infomaniak_lock_drive_user
Lock a kDrive user through POST /2/drive/{drive_id}/users/{user_id}/lock. Two-phase commit with current user guard. It is categorised as a Execute tool in the Infomaniak Admin MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Infomaniak Admin MCP server in PolicyLayer and add a rule for infomaniak_lock_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_lock_drive_user is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the infomaniak_lock_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_lock_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_lock_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.
Across the catalogue