AI agents use create_load_balancer to create or update resources in Hcloud — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Hcloud environment.
This tool creates a new load balancer resource in Hetzner Cloud infrastructure, which is reversible (the resource can be deleted). It does not execute arbitrary code, is not destructive (does not delete or overwrite), and does not move money. It is a Write operation that creates infrastructure as a service.
From the tool's definition Tool name is 'create_load_balancer' and description states 'Create a new load balancer'. The verb 'create' indicates data creation, which is a write operation. The context of Hetzner Cloud infrastructure confirms this creates a new resource.
Attacks that exploit this kind of access
Create a new load balancer. It is categorised as a Write tool in the Hcloud MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Hcloud MCP server in PolicyLayer and add a rule for create_load_balancer: 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 Hcloud. Nothing to install.
create_load_balancer 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_load_balancer 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_load_balancer. 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_load_balancer is provided by the Hcloud MCP server (xodus-co/hcloud-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →