List all Terragrunt stacks using experimental features
AI agents call list_stacks to retrieve information from Terragrunt GCP Tool MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and enumerates Terragrunt stacks without creating, modifying, or destroying any resources. It is purely informational, allowing inspection of the current infrastructure state. The experimental features reference does not change the fundamental read-only nature of listing. Misuse by an AI agent would have minimal blast radius—it can only expose what stacks exist, not alter them.
From the tool's definition Tool name 'list_stacks' and description 'List all Terragrunt stacks' indicate a retrieval operation with no side effects. The verb 'List' is a canonical Read operation that queries and returns existing infrastructure stack information.
Attacks that exploit this kind of access
List all Terragrunt stacks using experimental features. It is categorised as a Read tool in the Terragrunt GCP Tool MCP MCP Server, which means it retrieves data without modifying state.
Register the Terragrunt GCP Tool MCP server in PolicyLayer and add a rule for list_stacks: 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 GCP Tool MCP. Nothing to install.
list_stacks 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 list_stacks 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 list_stacks. 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.
list_stacks is provided by the Terragrunt GCP Tool MCP server (spolspol/terragrunt-gcp-tool-mcp). 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 →