infomaniak_manage_drive_private_directory
Update the maximum allowed size of kDrive private folders. Two-phase confirmation with a fresh settings snapshot; null removes the limit.
This record as markdown: /tools/henrikogaard-infomaniak-admin-mcp/infomaniak-manage-drive-private-directory.md
What infomaniak_manage_drive_private_directory does on Infomaniak Admin
AI agents use infomaniak_manage_drive_private_directory 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_manage_drive_private_directory is rated Medium
This tool modifies account settings (folder size limits) but does not delete data or cause irreversible damage. The change is reversible—limits can be adjusted back or removed. The two-phase confirmation mechanism further reduces risk. While this affects resource allocation for users, it remains a Write operation rather than Destructive.
From the tool's definition Tool description states 'Update the maximum allowed size of kDrive private folders' and 'null removes the limit', indicating reversible modification of configuration settings.
Attacks that exploit this kind of access
The rule that runs infomaniak_manage_drive_private_directory 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_manage_drive_private_directory, this is the rule to start with:
infomaniak_manage_drive_private_directory 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_manage_drive_private_directory call is checked against it from then on.
Questions about infomaniak_manage_drive_private_directory
Update the maximum allowed size of kDrive private folders. Two-phase confirmation with a fresh settings snapshot; null removes the limit. 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_manage_drive_private_directory: 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_manage_drive_private_directory 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_manage_drive_private_directory 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_manage_drive_private_directory. 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_manage_drive_private_directory 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