arvan_k8s_delete

kubectl delete -f a manifest or directory.

SERVERArvanCloud MCP Server SOURCEdwin-gharibi/arvancloud-mcp
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

Questions about arvan_k8s_delete

What does the arvan_k8s_delete tool do? +

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.

How do I enforce a policy on arvan_k8s_delete? +

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.

What risk level is arvan_k8s_delete? +

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.

Can I rate-limit arvan_k8s_delete? +

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.

How do I block arvan_k8s_delete completely? +

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.

What MCP server provides arvan_k8s_delete? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of ArvanCloud MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.