Diagnose Terragrunt and Terraform error messages with root cause analysis and solutions. Handles dependency cycles, state lock errors, provider issues, and HCL syntax problems.
AI agents call diagnose_terragrunt_error to retrieve information from Terragrunt MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and analyzes error information to provide diagnostic insights and solutions. It does not execute Terragrunt/Terraform commands, create or modify infrastructure, delete resources, or move money. The word 'diagnose' and the scope of analyzing error messages, dependency cycles, and syntax problems indicate a read-only informational operation.
From the tool's definition Tool performs diagnostic analysis and provides root cause analysis and solutions for error messages. The description indicates it diagnoses and handles existing errors (dependency cycles, state lock errors, provider issues, HCL syntax problems) without…
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
Diagnose Terragrunt and Terraform error messages with root cause analysis and solutions. Handles dependency cycles, state lock errors, provider issues, and HCL syntax problems. It is categorised as a Read tool in the Terragrunt MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Terragrunt MCP Server MCP server in PolicyLayer and add a rule for diagnose_terragrunt_error: 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 Terragrunt MCP Server. Nothing to install.
diagnose_terragrunt_error 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 diagnose_terragrunt_error 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 diagnose_terragrunt_error. 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.
diagnose_terragrunt_error is provided by the Terragrunt MCP Server MCP server (omattsson/terragrunt-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 →