Critical Risk →

delete-subnet

Delete a subnet by subnet ID in the given region

How to control delete-subnet ↓

What delete-subnet does on AWS MCP Server

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

Critical Risk

Why delete-subnet needs a policy

Deleting a subnet irreversibly removes a core networking resource and any associated configurations. This action cannot be undone without manual recovery or infrastructure restoration. The blast radius is high because a misconfigured deletion could disrupt production VPCs and dependent resources (EC2 instances, RDS databases). This fits the Destructive category as it permanently removes data/infrastructure.

From the tool's definition Tool name is 'delete-subnet' and description states 'Delete a subnet by subnet ID' — the verb 'delete' is explicit and indicates irreversible removal of network infrastructure.

Documented attack patterns abuse exactly the kind of access delete-subnet gives an agent:

How to control delete-subnet

PolicyLayer is an MCP gateway — it sits between your AI agents and AWS MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete-subnet:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete-subnet"
  ]
}

delete-subnet disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register AWS MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about delete-subnet

What does the delete-subnet tool do? +

Delete a subnet by subnet ID in the given region. It is categorised as a Destructive tool in the AWS 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-subnet? +

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

What risk level is delete-subnet? +

delete-subnet 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-subnet? +

Yes. Add a rate_limit block to the delete-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.

How do I block delete-subnet completely? +

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

What MCP server provides delete-subnet? +

delete-subnet is provided by the AWS MCP Server MCP server (lokeswaran-aj/aws-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every AWS MCP Server tool call.

Start from AWS MCP Server, 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.

54 AWS MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.