infomaniak_provision_site_full
Provision a complete website end-to-end: web site + MariaDB database + DNS A record. Two-phase commit at the workflow level. The plan lists every step that will run; on apply, each step is executed and reported in order so you can see partial completion if anything fails mid-way.
This record as markdown: /tools/henrikogaard-infomaniak-admin-mcp/infomaniak-provision-site-full.md
What infomaniak_provision_site_full does on Infomaniak Admin
AI agents invoke infomaniak_provision_site_full to trigger actions in Infomaniak Admin. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why infomaniak_provision_site_full is rated High
This tool executes a complex multi-step workflow that creates infrastructure resources and modifies DNS configurations. While it includes a two-phase commit for safety, the execution of provisioning steps with externally-visible side effects (creating websites, databases, DNS records) classifies it as Execute rather than Write.
From the tool's definition Tool performs 'Provision a complete website end-to-end: web site + MariaDB database + DNS A record' with 'each step is executed' in sequence.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs infomaniak_provision_site_full 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_provision_site_full, this is the rule to start with:
infomaniak_provision_site_full stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Infomaniak Admin, apply this rule, and every infomaniak_provision_site_full call is checked against it from then on.
Questions about infomaniak_provision_site_full
Provision a complete website end-to-end: web site + MariaDB database + DNS A record. Two-phase commit at the workflow level. The plan lists every step that will run; on apply, each step is executed and reported in order so you can see partial completion if anything fails mid-way. It is categorised as a Execute tool in the Infomaniak Admin MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Infomaniak Admin MCP server in PolicyLayer and add a rule for infomaniak_provision_site_full: 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_provision_site_full is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the infomaniak_provision_site_full 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_provision_site_full. 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_provision_site_full 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