infomaniak_delete_account_tag
Delete an account tag. Two-phase commit with a fresh tag snapshot guard.
This record as markdown: /tools/henrikogaard-infomaniak-admin-mcp/infomaniak-delete-account-tag.md
What infomaniak_delete_account_tag does on Infomaniak Admin
AI agents call infomaniak_delete_account_tag 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_delete_account_tag is rated Critical
This tool irreversibly removes data (an account tag) that cannot be automatically restored. While the two-phase commit provides some safety guardrails, deletion operations are categorized as Destructive per the classification rules. The severity is high rather than critical because the blast radius is limited to account tag metadata rather than core account data, user access, or financial systems.
From the tool's definition The tool name explicitly contains 'delete' and the description states it performs a 'Delete' operation on an account tag. The two-phase commit mechanism indicates the system recognizes this as a sensitive, irreversible operation requiring safeguards.
Attacks that exploit this kind of access
The rule that runs infomaniak_delete_account_tag 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_delete_account_tag, this is the rule to start with:
infomaniak_delete_account_tag 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_delete_account_tag call is checked against it from then on.
Questions about infomaniak_delete_account_tag
Delete an account tag. Two-phase commit with a fresh tag 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.
Register the Infomaniak Admin MCP server in PolicyLayer and add a rule for infomaniak_delete_account_tag: 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_delete_account_tag 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_delete_account_tag 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_delete_account_tag. 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_delete_account_tag 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