Fetch Terraform Registry best-practice guidance with optional provider/resource/module context.
AI agents call fetch_terraform_registry_guidance 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 retrieves guidance documentation from the Terraform Registry. It queries and returns information without creating, modifying, deleting, or executing any infrastructure changes. The 'fetch' operation is purely informational and read-only. Even in a broader context of a Terraform best-practices server, this specific tool performs no write, execute, or destructive actions.
From the tool's definition Tool name includes 'fetch' and description states 'Fetch Terraform Registry best-practice guidance' — both indicate data retrieval with no side effects.
Attacks that exploit this kind of access
Fetch Terraform Registry best-practice guidance with optional provider/resource/module context. 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 fetch_terraform_registry_guidance: 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.
fetch_terraform_registry_guidance 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 fetch_terraform_registry_guidance 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 fetch_terraform_registry_guidance. 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.
fetch_terraform_registry_guidance 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 →