update_load_balancer_service · Hcloud MCP: Risk & Policy

WHAT IT DOES

What update_load_balancer_service does on Hcloud

AI agents use update_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.

WHY IT NEEDS A POLICY

Why update_load_balancer_service needs a policy

This tool creates or modifies load balancer service configuration (listen_port, presumably other service parameters), which constitutes a Write operation. The changes are reversible (can be updated again or rolled back), so it does not rise to Destructive or Execute severity. Blast radius is medium as misconfiguration could disrupt load balancing and traffic routing, affecting service availability.

From the tool's definition The tool is named 'update_load_balancer_service' and described as updating a load balancer service, which modifies existing infrastructure configuration in a reversible manner.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_load_balancer_service Rate-limited

update_load_balancer_service 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_load_balancer_service": {
      "limits": [
        {
          "counter": "update_load_balancer_service_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Hcloud, so you can run agents against it safely.

FAQ

Questions about update_load_balancer_service

What does the update_load_balancer_service tool do? +

Update a load balancer service (listen_port identifies the service). 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.

How do I enforce a policy on update_load_balancer_service? +

Register the Hcloud MCP server in PolicyLayer and add a rule for update_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.

What risk level is update_load_balancer_service? +

update_load_balancer_service is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_load_balancer_service? +

Yes. Add a rate_limit block to the update_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.

How do I block update_load_balancer_service completely? +

Set action: deny in the PolicyLayer policy for update_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.

What MCP server provides update_load_balancer_service? +

update_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.