setup_load_balancer · MCP Software Engineer MCP

WHAT IT DOES

What setup_load_balancer does on MCP Software Engineer

AI agents invoke setup_load_balancer to trigger actions in MCP Software Engineer. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why setup_load_balancer needs a policy

Setting up a load balancer modifies live infrastructure configuration, affecting how traffic is routed across services. This is an Execute-level operation (triggering external infrastructure changes) with high severity because misconfiguration could disrupt service availability, expose internal services, or cause outages across the entire application stack.

From the tool's definition 'Setup load balancer configuration' — configuring a load balancer is an infrastructure operation that triggers external system changes affecting network routing and traffic distribution

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

setup_load_balancer Rate-limited

setup_load_balancer stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "setup_load_balancer": {
      "limits": [
        {
          "counter": "setup_load_balancer_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about setup_load_balancer

What does the setup_load_balancer tool do? +

Setup load balancer configuration. It is categorised as a Execute tool in the MCP Software Engineer MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on setup_load_balancer? +

Register the MCP Software Engineer MCP server in PolicyLayer and add a rule for setup_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 MCP Software Engineer. Nothing to install.

What risk level is setup_load_balancer? +

setup_load_balancer is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit setup_load_balancer? +

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

How do I block setup_load_balancer completely? +

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

What MCP server provides setup_load_balancer? +

setup_load_balancer is provided by the MCP Software Engineer MCP server (rajawatrajat/mcp-software-engineer). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.