arvan_delete_subnet
Delete a private-network subnet by id.
This record as markdown: /tools/dwin-gharibi-arvancloud-mcp/arvan-delete-subnet.md
What arvan_delete_subnet does on ArvanCloud MCP Server
AI agents call arvan_delete_subnet to permanently remove resources in ArvanCloud MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why arvan_delete_subnet is rated Critical
Deleting a subnet is a destructive action that cannot be undone and will sever network connectivity for any resources attached to it. This qualifies as Destructive per the classification rules. The severity is high because subnet deletion can cause widespread service outages and data loss if resources depend on that subnet, though it is not financial in nature.
From the tool's definition Tool name contains 'delete' and description states 'Delete a private-network subnet by id' — this is an irreversible operation that removes networking infrastructure.
Attacks that exploit this kind of access
The rule that runs arvan_delete_subnet safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ArvanCloud MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For arvan_delete_subnet, this is the rule to start with:
arvan_delete_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 ArvanCloud MCP Server, apply this rule, and every arvan_delete_subnet call is checked against it from then on.
Questions about arvan_delete_subnet
Delete a private-network subnet by id. It is categorised as a Destructive tool in the ArvanCloud MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the ArvanCloud MCP Server MCP server in PolicyLayer and add a rule for arvan_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 ArvanCloud MCP Server. Nothing to install.
arvan_delete_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 arvan_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.
Set action: deny in the PolicyLayer policy for arvan_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.
arvan_delete_subnet is provided by the ArvanCloud MCP Server MCP server (dwin-gharibi/arvancloud-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ArvanCloud MCP Server, and thousands of servers like it.
Across the catalogue