delete_vpc2

THE RISK

Critical Risk

Why delete_vpc2 needs a policy

Deleting a VPC 2.0 network is an irreversible destructive action. Removing a network could disrupt connectivity for all resources attached to it, potentially taking down services, compute instances, and databases that depend on that network. The blast radius is high as it affects network infrastructure.

From the tool's definition 'Delete a VPC 2.0 network' — explicitly deletes a virtual private cloud network

Documented attack patterns abuse exactly the kind of access delete_vpc2 gives an agent:

POLICY

How to control delete_vpc2

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

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_vpc2"
  ]
}

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

Create a free account and register Vultr MCP — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Vultr MCP tools

Destructive delete Delete a block storage volume. Destructive delete_bare_metal_server Delete a bare metal server. Destructive delete_cdn_ssl_certificate Remove SSL certificate from a CDN zone. Destructive delete_cdn_zone Delete a CDN zone. Destructive delete_collection delete_collection Destructive delete_connection_pool Delete a connection pool. Destructive delete_dns_domain Delete a DNS domain and ALL its associated records Destructive delete_dns_record Delete a specific DNS record

All 284 Vultr MCP tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in Vultr MCP → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about delete_vpc2

What does the delete_vpc2 tool do? +

Delete a VPC 2.0 network. It is categorised as a Destructive tool in the Vultr MCP 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_vpc2? +

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

What risk level is delete_vpc2? +

delete_vpc2 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_vpc2? +

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

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

delete_vpc2 is provided by the Vultr MCP server (rsp2k/mcp-vultr). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Vultr MCP tool call.

Start from Vultr MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →