create_loadbalancer
AI agents use create_loadbalancer to create or update resources in Sacloud — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Sacloud environment.
Creating a load balancer is a write operation that adds a new cloud infrastructure component. While the blast radius is significant (a misconfigured load balancer could misdirect traffic or cause service disruption), the operation is reversible via deletion (delete operations exist on this server).
From the tool's definition Tool name 'create_loadbalancer' indicates it creates a new cloud resource. The server description states it 'enables interaction with cloud resources', and sibling tools like 'create_disk', 'create_server', 'create_switch', 'create_router' all perform Write…
Documented attack patterns abuse exactly the kind of access create_loadbalancer gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Sacloud, and nothing reaches the server without passing your rules. This is the rule we recommend for create_loadbalancer:
{
"version": "1",
"default": "deny",
"tools": {
"create_loadbalancer": {
"limits": [
{
"counter": "create_loadbalancer_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_loadbalancer 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.
Free to start. No card required.
create_loadbalancer. It is categorised as a Write tool in the Sacloud MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Sacloud MCP server in PolicyLayer and add a rule for create_loadbalancer: 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 Sacloud. Nothing to install.
create_loadbalancer 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 create_loadbalancer 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 create_loadbalancer. 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.
create_loadbalancer is provided by the Sacloud MCP server (sacloud/sacloud-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Sacloud, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
37 Sacloud tools catalogued and risk-classified — across an index of 43,000+ MCP servers.