Delete a subnet from a network (detach servers from it first)
AI agents call delete_network_subnet to permanently remove resources in Hcloud — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool performs an irreversible deletion of a network subnet, which cannot be undone. Deletion of cloud infrastructure resources is a destructive operation with significant blast radius—loss of network configuration, potential service disruption, and data isolation. While not as critical as account-level destruction, subnet deletion is a high-severity destructive action in cloud infrastructure management.
From the tool's definition Tool name is 'delete_network_subnet' and description states 'Delete a subnet from a network'. The use of 'delete' indicates irreversible removal of infrastructure resources.
Attacks that exploit this kind of access
Delete a subnet from a network (detach servers from it first). It is categorised as a Destructive tool in the Hcloud MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Hcloud MCP server in PolicyLayer and add a rule for delete_network_subnet: 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 Hcloud. Nothing to install.
delete_network_subnet is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_network_subnet 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 delete_network_subnet. 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.
delete_network_subnet is provided by the Hcloud MCP server (xodus-co/hcloud-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the 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 →