New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

infomaniak_remove_drive_file_access_user

Revoke a user

SERVERInfomaniak Admin SOURCEhenrikogaard/infomaniak-admin-mcp
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

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

What infomaniak_remove_drive_file_access_user does on Infomaniak Admin

AI agents call infomaniak_remove_drive_file_access_user to permanently remove resources in Infomaniak Admin, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why infomaniak_remove_drive_file_access_user is rated Critical

Revoking access is not easily reversible in most systems; it removes an established permission grant. This falls under Destructive rather than Write because the operation eliminates access rights that must be explicitly re-granted. High severity because an AI agent could inadvertently revoke access for legitimate users, causing loss of access to files.

From the tool's definition 'Revoke a user' — removing/revoking access is an irreversible action that eliminates a user's permissions to a drive file

Questions about infomaniak_remove_drive_file_access_user

What does the infomaniak_remove_drive_file_access_user tool do? +

Revoke a user. It is categorised as a Destructive tool in the Infomaniak Admin MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on infomaniak_remove_drive_file_access_user? +

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

What risk level is infomaniak_remove_drive_file_access_user? +

infomaniak_remove_drive_file_access_user is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit infomaniak_remove_drive_file_access_user? +

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

How do I block infomaniak_remove_drive_file_access_user completely? +

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

What MCP server provides infomaniak_remove_drive_file_access_user? +

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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Infomaniak Admin's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.