delete_load_balancer_rule

Delete a load balancer rule

Server CloudStack MCP Server mozg31337/cloudstack-mcp-server
Category Destructive
Risk class Critical
Parameters 00 required

What delete_load_balancer_rule does on CloudStack MCP Server

AI agents call delete_load_balancer_rule to permanently remove resources in CloudStack MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why delete_load_balancer_rule needs a policy

Deleting a load balancer rule is an irreversible operation that removes network routing configuration. This fits the Destructive category as the action cannot be undone and has immediate operational impact on traffic routing. While the server provides a safety confirmation system for destructive operations (mentioned in server description), the tool itself performs permanent deletion.

From the tool's definition Tool name explicitly contains 'delete'; description states 'Delete a load balancer rule', confirming irreversible removal of infrastructure configuration.

Questions about delete_load_balancer_rule

What does the delete_load_balancer_rule tool do? +

Delete a load balancer rule. It is categorised as a Destructive tool in the CloudStack MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on delete_load_balancer_rule? +

Register the CloudStack MCP Server MCP server in PolicyLayer and add a rule for delete_load_balancer_rule: 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 CloudStack MCP Server. Nothing to install.

What risk level is delete_load_balancer_rule? +

delete_load_balancer_rule is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_load_balancer_rule? +

Yes. Add a rate_limit block to the delete_load_balancer_rule 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 delete_load_balancer_rule completely? +

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

delete_load_balancer_rule is provided by the CloudStack MCP Server MCP server (mozg31337/cloudstack-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.