arvan_k8s_delete
kubectl delete -f a manifest or directory.
This record as markdown: /tools/dwin-gharibi-arvancloud-mcp/arvan-k8s-delete.md
What arvan_k8s_delete does on ArvanCloud MCP Server
AI agents call arvan_k8s_delete 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_k8s_delete is rated Critical
This tool performs irreversible deletion of Kubernetes resources. While not financial in nature, it has a high blast radius due to the permanent loss of infrastructure and potential application downtime. It is classified as Destructive rather than Execute because the deletion cannot be reversed—the primary consequence is permanent resource removal, which is the defining characteristic of the Destructive category.
From the tool's definition Tool executes 'kubectl delete -f' which irreversibly deletes Kubernetes resources defined in a manifest or directory. The 'delete' operation cannot be undone and permanently removes cloud infrastructure, pods, services, and configurations.
Attacks that exploit this kind of access
The rule that runs arvan_k8s_delete 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_k8s_delete, this is the rule to start with:
arvan_k8s_delete 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_k8s_delete call is checked against it from then on.
Questions about arvan_k8s_delete
kubectl delete -f a manifest or directory. 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_k8s_delete: 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_k8s_delete 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_k8s_delete 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_k8s_delete. 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_k8s_delete 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