infomaniak_update_drive_share_link
Update a kDrive share link through PUT /2/drive/{drive_id}/files/{file_id}/link. Two-phase commit with current share-link guard.
This record as markdown: /tools/henrikogaard-infomaniak-admin-mcp/infomaniak-update-drive-share-link.md
What infomaniak_update_drive_share_link does on Infomaniak Admin
AI agents use infomaniak_update_drive_share_link 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_update_drive_share_link is rated Medium
This tool creates or modifies data (share link settings) in a reversible manner. It does not delete data (would be Destructive), execute arbitrary code (would be Execute), or involve financial transactions (would be Financial). The PUT endpoint and 'Update' verb confirm it is a Write operation.
From the tool's definition Tool description explicitly states 'Update a kDrive share link' via PUT method, which modifies existing share link configuration.
Attacks that exploit this kind of access
The rule that runs infomaniak_update_drive_share_link 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_share_link, this is the rule to start with:
infomaniak_update_drive_share_link 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_update_drive_share_link call is checked against it from then on.
Questions about infomaniak_update_drive_share_link
Update a kDrive share link through PUT /2/drive/{drive_id}/files/{file_id}/link. Two-phase commit with current share-link 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_update_drive_share_link: 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_update_drive_share_link 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_update_drive_share_link 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_update_drive_share_link. 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_update_drive_share_link 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