delete_ipv4_subnet_for_zone

Delete IPv4 subnet for zone

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

What delete_ipv4_subnet_for_zone does on CloudStack MCP Server

AI agents call delete_ipv4_subnet_for_zone 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_ipv4_subnet_for_zone needs a policy

Deleting an IPv4 subnet for a zone is a destructive operation that cannot be undone. It removes network configuration and may affect running services, making it a high-severity destructive action. The CloudStack server's mention of 'safety confirmation system for destructive operations' confirms this falls into the destructive category.

From the tool's definition Tool name is 'delete_ipv4_subnet_for_zone' with description 'Delete IPv4 subnet for zone' — the verb 'delete' indicates irreversible removal of network infrastructure.

Questions about delete_ipv4_subnet_for_zone

What does the delete_ipv4_subnet_for_zone tool do? +

Delete IPv4 subnet for zone. 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_ipv4_subnet_for_zone? +

Register the CloudStack MCP Server MCP server in PolicyLayer and add a rule for delete_ipv4_subnet_for_zone: 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_ipv4_subnet_for_zone? +

delete_ipv4_subnet_for_zone 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_ipv4_subnet_for_zone? +

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

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

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

// THE FULL RECORD

delete_ipv4_subnet_for_zone is one line of CloudStack MCP Server's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

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.