delete_vpc_subnet
Delete a subnet in a VPC
This record as markdown: /tools/takashito-linode-mcp-server/delete-vpc-subnet.md
What delete_vpc_subnet does on Linode MCP Server
AI agents call delete_vpc_subnet to permanently remove resources in Linode MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why delete_vpc_subnet is rated Critical
This tool permanently removes a VPC subnet and its associated configuration from Linode infrastructure. Deletion of network infrastructure is irreversible and could disrupt services, isolate compute instances, or cause data access issues. While not directly financial, the blast radius is significant as it affects network topology and availability of dependent resources.
From the tool's definition Tool name 'delete_vpc_subnet' and description 'Delete a subnet in a VPC' explicitly perform a deletion operation that cannot be reversed.
Attacks that exploit this kind of access
The rule that runs delete_vpc_subnet safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Linode MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_vpc_subnet, this is the rule to start with:
delete_vpc_subnet is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Linode MCP Server, apply this rule, and every delete_vpc_subnet call is checked against it from then on.
Questions about delete_vpc_subnet
Delete a subnet in a VPC. It is categorised as a Destructive tool in the Linode MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Linode MCP Server MCP server in PolicyLayer and add a rule for delete_vpc_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 Linode MCP Server. Nothing to install.
delete_vpc_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_vpc_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_vpc_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_vpc_subnet is provided by the Linode MCP Server MCP server (takashito/linode-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Linode MCP Server, and thousands of servers like it.
Across the catalogue