infomaniak_delete_site_alias
Remove one alias FQDN from a web hosting site (the main FQDN cannot be removed). Two-phase commit. After this, the site
This record as markdown: /tools/henrikogaard-infomaniak-admin-mcp/infomaniak-delete-site-alias.md
What infomaniak_delete_site_alias does on Infomaniak Admin
AI agents call infomaniak_delete_site_alias 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_site_alias is rated Critical
The tool permanently removes a domain alias from a web hosting site. While not catastrophic (the main FQDN is protected), deleting aliases is an irreversible action that destroys configuration state. This falls squarely into the Destructive category. The two-phase commit mitigates risk somewhat but does not change the fundamental destructive nature of the operation.
From the tool's definition Tool name includes 'delete' and description states 'Remove one alias FQDN from a web hosting site' - this is an irreversible deletion operation that cannot be undone.
Attacks that exploit this kind of access
The rule that runs infomaniak_delete_site_alias 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_site_alias, this is the rule to start with:
infomaniak_delete_site_alias 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_site_alias call is checked against it from then on.
Questions about infomaniak_delete_site_alias
Remove one alias FQDN from a web hosting site (the main FQDN cannot be removed). Two-phase commit. After this, the site. 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_site_alias: 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_site_alias 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_site_alias 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_site_alias. 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_site_alias 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