Generate markdown documentation for Terraform modules from source code.
AI agents call generate_terraform_module_docs 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 reads Terraform source code and generates documentation output (markdown). It does not modify files, execute commands, or have destructive effects — it produces a read-only artifact from existing source. The main risk is minor: it reads source code, but has no meaningful blast radius if misused.
From the tool's definition Generate markdown documentation for Terraform modules from source code
Attacks that exploit this kind of access
Generate markdown documentation for Terraform modules from source code. 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 generate_terraform_module_docs: 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.
generate_terraform_module_docs 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 generate_terraform_module_docs 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 generate_terraform_module_docs. 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.
generate_terraform_module_docs 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 →