AI agents call list_load_balancer_types to retrieve information from Hcloud without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves and presents available load balancer type options from the Hetzner Cloud API. It has no side effects, does not modify any resources, and serves purely an informational purpose to support decision-making in other tools like create_load_balancer. The blast radius of misuse is minimal—an agent could only obtain knowledge about available types, not affect infrastructure.
From the tool's definition Tool name contains 'list' and description states 'List all load balancer types', indicating a query operation that retrieves information without modification.
Attacks that exploit this kind of access
List all load balancer types (for create_load_balancer load_balancer_type). It is categorised as a Read tool in the Hcloud MCP Server, which means it retrieves data without modifying state.
Register the Hcloud MCP server in PolicyLayer and add a rule for list_load_balancer_types: 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.
list_load_balancer_types is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_load_balancer_types 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 list_load_balancer_types. 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.
list_load_balancer_types 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 →