infomaniak_create_drive_file_access_user
Grant a user access to a kDrive file or folder. Two-phase commit with current file-access guard.
This record as markdown: /tools/henrikogaard-infomaniak-admin-mcp/infomaniak-create-drive-file-access-user.md
What infomaniak_create_drive_file_access_user does on Infomaniak Admin
AI agents use infomaniak_create_drive_file_access_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_create_drive_file_access_user is rated Medium
This tool creates new access control relationships (granting permissions) which is a reversible Write operation. It modifies data (access control lists) but does not delete or irreversibly destroy anything. The two-phase commit mechanism and access guard mitigate risk somewhat, but granting unintended file access in a multi-user system could expose sensitive data to unauthorized users.
From the tool's definition Tool grants user access to kDrive file or folder, explicitly a permission/access modification. Description states "Grant a user access" and "Two-phase commit with current file-access guard" — this creates or modifies access control entries reversibly.
Attacks that exploit this kind of access
The rule that runs infomaniak_create_drive_file_access_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_create_drive_file_access_user, this is the rule to start with:
infomaniak_create_drive_file_access_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_create_drive_file_access_user call is checked against it from then on.
Questions about infomaniak_create_drive_file_access_user
Grant a user access to a kDrive file or folder. Two-phase commit with current file-access 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_create_drive_file_access_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_create_drive_file_access_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_create_drive_file_access_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_create_drive_file_access_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_create_drive_file_access_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