Analyze Terraform code structure, modularity, variables, and best practices.
AI agents call analyze_terraform_code to retrieve information from Terraform Best Practices without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs static analysis of Terraform code to evaluate its structure and adherence to best practices. It retrieves and examines existing code without creating, modifying, executing, or deleting any infrastructure or data. The verb 'analyze' combined with the scope (code structure, modularity, variables, best practices) confirms this is a read-only operation.
From the tool's definition The tool description states it 'Analyze[s] Terraform code structure, modularity, variables, and best practices' — pure analysis with no modifications, execution, or side effects.
Attacks that exploit this kind of access
Analyze Terraform code structure, modularity, variables, and best practices. It is categorised as a Read tool in the Terraform Best Practices MCP Server, which means it retrieves data without modifying state.
Register the Terraform Best Practices MCP server in PolicyLayer and add a rule for analyze_terraform_code: 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 Best Practices. Nothing to install.
analyze_terraform_code is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the analyze_terraform_code 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 analyze_terraform_code. 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.
analyze_terraform_code is provided by the Terraform Best Practices MCP server (@downatthebottomofthemolehole/terraform-best-practices-mcp-server). 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 →