create_hetzner_server
Create a Hetzner Cloud server and register it in Coolify.
This record as markdown: /tools/coolify/create-hetzner-server.md
What create_hetzner_server does on Coolify
AI agents use create_hetzner_server to create or update resources in Coolify, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Coolify environment.
Why create_hetzner_server is rated Medium
This tool provisions a new cloud server on Hetzner Cloud and registers it in Coolify. It creates real infrastructure resources which incur costs, but does not directly move money or commit financial obligations in a payment sense — it is a Write/provisioning action.
From the tool's definition Create a Hetzner Cloud server and register it in Coolify
Attacks that exploit this kind of access
The rule that runs create_hetzner_server safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Coolify, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_hetzner_server, this is the rule to start with:
create_hetzner_server 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Coolify, apply this rule, and every create_hetzner_server call is checked against it from then on.
Questions about create_hetzner_server
Create a Hetzner Cloud server and register it in Coolify. It is categorised as a Write tool in the Coolify MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Coolify MCP server in PolicyLayer and add a rule for create_hetzner_server: 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 Coolify. Nothing to install.
create_hetzner_server is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_hetzner_server 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 create_hetzner_server. 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.
create_hetzner_server is provided by the Coolify MCP server (coolify-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Coolify, and thousands of servers like it.
This server
Across the catalogue