infomaniak_update_drive_user

Update a kDrive user through PUT /2/drive/{drive_id}/users/{user_id}. Two-phase commit with current user guard.

SERVERInfomaniak Admin SOURCEhenrikogaard/infomaniak-admin-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/henrikogaard-infomaniak-admin-mcp/infomaniak-update-drive-user.md

WHAT IT DOES

What infomaniak_update_drive_user does on Infomaniak Admin

AI agents use infomaniak_update_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.

RISK

Why infomaniak_update_drive_user is rated Medium

This tool modifies user data and potentially access controls reversibly (users can be updated again). It is not destructive (data is not deleted), not financial, and not execute (no arbitrary code/command execution). The 'high' severity reflects that unauthorized user updates could grant/revoke access to sensitive shared storage, affecting multiple users.

From the tool's definition Tool description explicitly states 'Update a kDrive user through PUT /2/drive/{drive_id}/users/{user_id}' — PUT is an HTTP method used for modifying existing resources. The operation updates user properties/permissions within a shared kDrive storage system.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs infomaniak_update_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_update_drive_user, this is the rule to start with:

infomaniak_update_drive_user Rate-limited

infomaniak_update_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "infomaniak_update_drive_user": {
      "limits": [
        {
          "counter": "infomaniak_update_drive_user_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Infomaniak Admin, apply this rule, and every infomaniak_update_drive_user call is checked against it from then on.

FAQ

Questions about infomaniak_update_drive_user

What does the infomaniak_update_drive_user tool do? +

Update a kDrive user through PUT /2/drive/{drive_id}/users/{user_id}. 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.

How do I enforce a policy on infomaniak_update_drive_user? +

Register the Infomaniak Admin MCP server in PolicyLayer and add a rule for infomaniak_update_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.

What risk level is infomaniak_update_drive_user? +

infomaniak_update_drive_user is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit infomaniak_update_drive_user? +

Yes. Add a rate_limit block to the infomaniak_update_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.

How do I block infomaniak_update_drive_user completely? +

Set action: deny in the PolicyLayer policy for infomaniak_update_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.

What MCP server provides infomaniak_update_drive_user? +

infomaniak_update_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.

KEEP EXPLORING

More on Infomaniak Admin, and thousands of servers like it.

This server

All 217 Infomaniak Admin tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP →team_manager_update_budget on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →