Destroy Terraform resources
AI agents call tf_destroy to permanently remove resources in Terraform MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
tf_destroy performs irreversible deletion of cloud infrastructure resources managed by Terraform. This is the most severe category (Destructive > Execute > Write > Read) because the effects cannot be undone—destroyed resources are gone unless restored from external backups.
From the tool's definition Tool name is 'tf_destroy' with description 'Destroy Terraform resources'. The destroy action in Terraform irreversibly terminates and removes infrastructure resources (compute instances, databases, networks, etc.) that cannot be recovered without manual…
Attacks that exploit this kind of access
Destroy Terraform resources. It is categorised as a Destructive tool in the Terraform MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Terraform MCP Server MCP server in PolicyLayer and add a rule for tf_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 Terraform MCP Server. Nothing to install.
tf_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 tf_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 tf_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.
tf_destroy is provided by the Terraform MCP Server MCP server (mjrestivo16/mcp-terraform). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →