Get detailed information about a specific stack including units and execution order
AI agents call get_stack_details 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 queries stack metadata and configuration details. It performs no creation, modification, deletion, or execution of infrastructure changes—it is purely informational. The lack of action verbs like 'create', 'update', 'delete', or 'apply' confirms it is a Read operation with minimal blast radius if misused by an AI agent.
From the tool's definition Tool name 'get_stack_details' and description 'Get detailed information about a specific stack' indicate a retrieval operation with no modification.
Attacks that exploit this kind of access
Get detailed information about a specific stack including units and execution order. 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 get_stack_details: 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.
get_stack_details 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 get_stack_details 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 get_stack_details. 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.
get_stack_details 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 →