infomaniak_cancel_user_pending_invitations
Cancel pending account invitations for a user. Two-phase commit: first call returns the pending invitation list and confirmation token; second call deletes only invitations still pending in the fresh apply prefetch.
This record as markdown: /tools/henrikogaard-infomaniak-admin-mcp/infomaniak-cancel-user-pending-invitations.md
What infomaniak_cancel_user_pending_invitations does on Infomaniak Admin
AI agents call infomaniak_cancel_user_pending_invitations 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_cancel_user_pending_invitations is rated Critical
This tool permanently deletes pending invitation records, which cannot be undone. While the two-phase commit pattern provides a safety mechanism to verify the action before execution, the fundamental operation is destructive in nature. The invitations must be re-created to restore them, making this a Destructive action rather than simply a Write.
From the tool's definition 'Cancel pending account invitations' and 'second call deletes only invitations' - the tool irreversibly removes pending invitations from the user's account.
Attacks that exploit this kind of access
The rule that runs infomaniak_cancel_user_pending_invitations 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_cancel_user_pending_invitations, this is the rule to start with:
infomaniak_cancel_user_pending_invitations is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Infomaniak Admin, apply this rule, and every infomaniak_cancel_user_pending_invitations call is checked against it from then on.
Questions about infomaniak_cancel_user_pending_invitations
Cancel pending account invitations for a user. Two-phase commit: first call returns the pending invitation list and confirmation token; second call deletes only invitations still pending in the fresh apply prefetch. 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.
Register the Infomaniak Admin MCP server in PolicyLayer and add a rule for infomaniak_cancel_user_pending_invitations: 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_cancel_user_pending_invitations is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the infomaniak_cancel_user_pending_invitations 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_cancel_user_pending_invitations. 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_cancel_user_pending_invitations 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.
Across the catalogue