destroy_tf_project_infrastructure

Run

Server Infrastructure Auto Provisioner zerosync-co/mcp-server-autoprovisioner
Category Destructive
Risk class Critical
Parameters 00 required

What destroy_tf_project_infrastructure does on Infrastructure Auto Provisioner

AI agents call destroy_tf_project_infrastructure to permanently remove resources in Infrastructure Auto Provisioner — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why destroy_tf_project_infrastructure needs a policy

This tool destroys infrastructure (likely Terraform-managed cloud resources), which is an irreversible operation that cannot be undone. The blast radius is critical as it can result in complete loss of running systems, data stores, and services. Misuse by an AI agent could cause severe business continuity impact, data loss, and financial damage from service interruption.

From the tool's definition Tool name 'destroy_tf_project_infrastructure' explicitly indicates deletion/destruction of infrastructure resources. The verb 'destroy' combined with 'infrastructure' indicates irreversible removal of deployed resources.

Questions about destroy_tf_project_infrastructure

What does the destroy_tf_project_infrastructure tool do? +

Run. It is categorised as a Destructive tool in the Infrastructure Auto Provisioner 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 destroy_tf_project_infrastructure? +

Register the Infrastructure Auto Provisioner MCP server in PolicyLayer and add a rule for destroy_tf_project_infrastructure: 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 Infrastructure Auto Provisioner. Nothing to install.

What risk level is destroy_tf_project_infrastructure? +

destroy_tf_project_infrastructure 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 destroy_tf_project_infrastructure? +

Yes. Add a rate_limit block to the destroy_tf_project_infrastructure 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 destroy_tf_project_infrastructure completely? +

Set action: deny in the PolicyLayer policy for destroy_tf_project_infrastructure. 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 destroy_tf_project_infrastructure? +

destroy_tf_project_infrastructure is provided by the Infrastructure Auto Provisioner MCP server (zerosync-co/mcp-server-autoprovisioner). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.