infomaniak_remove_account_team_users

Remove one or more users from an account team. Two-phase commit with a fresh team-members snapshot guard.

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-account-team-users.md

WHAT IT DOES

What infomaniak_remove_account_team_users does on Infomaniak Admin

AI agents call infomaniak_remove_account_team_users 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.

RISK

Why infomaniak_remove_account_team_users is rated Critical

Removing users from an account team revokes their access and membership, which is an irreversible destructive action. While a user could theoretically be re-added, the act of removal itself has immediate destructive consequences (loss of access, permissions, etc.) and cannot be automatically undone. The two-phase commit guard reduces risk of accidental misuse but doesn't change the category.

From the tool's definition 'Remove one or more users from an account team' — removal of users is an irreversible access revocation action

Attacks that exploit this kind of access

RECOMMENDED RULE

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

infomaniak_remove_account_team_users Hidden

infomaniak_remove_account_team_users is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "infomaniak_remove_account_team_users"
  ]
}

RESTRICT 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_remove_account_team_users call is checked against it from then on.

FAQ

Questions about infomaniak_remove_account_team_users

What does the infomaniak_remove_account_team_users tool do? +

Remove one or more users from an account team. Two-phase commit with a fresh team-members snapshot guard. 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_account_team_users? +

Register the Infomaniak Admin MCP server in PolicyLayer and add a rule for infomaniak_remove_account_team_users: 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_account_team_users? +

infomaniak_remove_account_team_users 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_account_team_users? +

Yes. Add a rate_limit block to the infomaniak_remove_account_team_users 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_account_team_users completely? +

Set action: deny in the PolicyLayer policy for infomaniak_remove_account_team_users. 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_account_team_users? +

infomaniak_remove_account_team_users 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 → Critical-risk tools on this server →

Across the catalogue

team_manager_reset on Team Manager MCP →remove_video on Mcptube Vision →delete_email_account on cPanel MCP Server →remove_concept on MegaMemory → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →