Apply Terraform changes
AI agents invoke tf_apply to trigger actions in Terraform MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Applying Terraform changes executes real infrastructure operations (creating, modifying, or destroying cloud resources). While it can be destructive, the primary action is execution of infrastructure-as-code changes whose effects depend on the current plan/configuration. Misuse could provision costly resources, expose security groups, or alter production infrastructure at massive scale, warranting critical severity.
From the tool's definition 'Apply Terraform changes' — tf_apply executes infrastructure provisioning, modification, and potentially destructive changes across cloud resources
Attacks that exploit this kind of access
Apply Terraform changes. It is categorised as a Execute tool in the Terraform MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Terraform MCP Server MCP server in PolicyLayer and add a rule for tf_apply: 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_apply is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the tf_apply 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_apply. 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_apply 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 →