assign_to_load_balancer_rule

What assign_to_load_balancer_rule does on CloudStack MCP Server

AI agents use assign_to_load_balancer_rule to create or update resources in CloudStack MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your CloudStack MCP Server environment.

Why assign_to_load_balancer_rule is rated Medium

Assigning VMs to load balancer rules modifies the active traffic routing configuration and network load distribution. This is reversible (VMs can be removed from rules), so it is Write rather than Destructive. However, the blast radius is high because incorrect assignments could disrupt network traffic, impact service availability, and affect multiple customer-facing systems.

From the tool's definition Assigns virtual machines to load balancer rule: the tool 'assign_to_load_balancer_rule' creates or modifies network load balancing configuration by associating VM instances with a load balancer rule. This is a write operation that changes infrastructure state.

The rule that runs assign_to_load_balancer_rule safely

PolicyLayer is an MCP gateway: it sits between your AI agents and CloudStack MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For assign_to_load_balancer_rule, this is the rule to start with:

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

Questions about assign_to_load_balancer_rule