AI agents use add_load_balancer_service 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 adds a service to an existing load balancer, which is a reversible modification operation. It creates new configuration state but does not delete, execute arbitrary code, or move financial resources. The blast radius is moderate: misconfiguration could route traffic incorrectly or disrupt service availability, but the operation itself is not destructive and can be reversed by removing the service.
From the tool's definition Tool name 'add_load_balancer_service' and description 'Add a service to a load balancer' indicate the action creates or modifies a load balancer configuration by adding a new service resource.
Attacks that exploit this kind of access
Add a service to a 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 add_load_balancer_service: 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.
add_load_balancer_service 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 add_load_balancer_service 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 add_load_balancer_service. 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.
add_load_balancer_service 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 →