infomaniak_add_account_team_users
Add one or more users to an account team. Two-phase commit with a fresh team-members snapshot guard.
This record as markdown: /tools/henrikogaard-infomaniak-admin-mcp/infomaniak-add-account-team-users.md
What infomaniak_add_account_team_users does on Infomaniak Admin
AI agents use infomaniak_add_account_team_users 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_add_account_team_users is rated Medium
This tool creates or modifies team membership data by adding users to an account team. This is a Write operation—it changes account state reversibly (users can be removed later). While it affects access control and team composition, it does not delete data or move financial resources, so Write is the appropriate category rather than Execute or higher.
From the tool's definition The tool description states it 'Add[s] one or more users to an account team', which is a reversible modification operation. The mention of 'two-phase commit with a fresh team-members snapshot guard' indicates write-like behavior with safety mechanisms.
Attacks that exploit this kind of access
The rule that runs infomaniak_add_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_add_account_team_users, this is the rule to start with:
infomaniak_add_account_team_users 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_add_account_team_users call is checked against it from then on.
Questions about infomaniak_add_account_team_users
Add one or more users to an account team. Two-phase commit with a fresh team-members snapshot 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_add_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.
infomaniak_add_account_team_users 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_add_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.
Set action: deny in the PolicyLayer policy for infomaniak_add_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.
infomaniak_add_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.
More on Infomaniak Admin, and thousands of servers like it.
This server
Across the catalogue