New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

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

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-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.

Questions about infomaniak_delete_site_alias

What does the infomaniak_delete_site_alias tool do? +

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.

How do I enforce a policy on infomaniak_delete_site_alias? +

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.

What risk level is infomaniak_delete_site_alias? +

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.

Can I rate-limit infomaniak_delete_site_alias? +

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.

How do I block infomaniak_delete_site_alias completely? +

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.

What MCP server provides infomaniak_delete_site_alias? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Infomaniak Admin's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.