arvan_iac_terraform_destroy
Run terraform destroy (tears down infrastructure; needs auto_approve).
This record as markdown: /tools/dwin-gharibi-arvancloud-mcp/arvan-iac-terraform-destroy.md
What arvan_iac_terraform_destroy does on ArvanCloud MCP Server
AI agents call arvan_iac_terraform_destroy 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_iac_terraform_destroy is rated Critical
terraform destroy is inherently destructive - it permanently deletes infrastructure resources that cannot be easily restored. Unlike reversible write operations, this causes data loss and service unavailability. The blast radius is critical: an AI agent invoking this without proper safeguards could destroy an entire production environment, databases, storage, networking, and compute resources simultaneously.
From the tool's definition The tool explicitly runs ``terraform destroy`` which "tears down infrastructure" - this is an irreversible destruction operation that removes cloud resources. The note about "needs auto_approve" confirms the destructive nature requires explicit authorization.
Attacks that exploit this kind of access
The rule that runs arvan_iac_terraform_destroy 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_iac_terraform_destroy, this is the rule to start with:
arvan_iac_terraform_destroy 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_iac_terraform_destroy call is checked against it from then on.
Questions about arvan_iac_terraform_destroy
Run terraform destroy (tears down infrastructure; needs auto_approve). 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_iac_terraform_destroy: 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_iac_terraform_destroy 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_iac_terraform_destroy 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_iac_terraform_destroy. 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_iac_terraform_destroy 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