infomaniak_add_site_aliases

Bind one or more additional FQDNs (including wildcards like

SERVERInfomaniak Admin SOURCEhenrikogaard/infomaniak-admin-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/henrikogaard-infomaniak-admin-mcp/infomaniak-add-site-aliases.md

WHAT IT DOES

What infomaniak_add_site_aliases does on Infomaniak Admin

AI agents use infomaniak_add_site_aliases 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.

RISK

Why infomaniak_add_site_aliases is rated Medium

This tool creates or adds new site aliases/FQDNs to a hosting account, which is a reversible modification of configuration data. It does not delete data (ruling out Destructive), does not execute arbitrary code (ruling out Execute), involves no financial transactions, and creates new bindings rather than merely reading.

From the tool's definition Tool name 'infomaniak_add_site_aliases' indicates creation of additional domain bindings. Description states 'Bind one or more additional FQDNs (including wildcards like' suggesting adding new DNS/site aliases to an account.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs infomaniak_add_site_aliases 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_site_aliases, this is the rule to start with:

infomaniak_add_site_aliases Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "infomaniak_add_site_aliases": {
      "limits": [
        {
          "counter": "infomaniak_add_site_aliases_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Infomaniak Admin, apply this rule, and every infomaniak_add_site_aliases call is checked against it from then on.

FAQ

Questions about infomaniak_add_site_aliases

What does the infomaniak_add_site_aliases tool do? +

Bind one or more additional FQDNs (including wildcards like. 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.

How do I enforce a policy on infomaniak_add_site_aliases? +

Register the Infomaniak Admin MCP server in PolicyLayer and add a rule for infomaniak_add_site_aliases: 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_add_site_aliases? +

infomaniak_add_site_aliases is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit infomaniak_add_site_aliases? +

Yes. Add a rate_limit block to the infomaniak_add_site_aliases 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_add_site_aliases completely? +

Set action: deny in the PolicyLayer policy for infomaniak_add_site_aliases. 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_add_site_aliases? +

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

KEEP EXPLORING

More on Infomaniak Admin, and thousands of servers like it.

This server

All 217 Infomaniak Admin tools →

Across the catalogue

add-tag on Kanban MCP Server →kb_add on Persistent Kb → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →