Analyze resource dependencies
AI agents call analyze_dependencies 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.
The tool performs dependency analysis, which is a read-only operation that retrieves and examines existing infrastructure state and relationships. It has no side effects on cloud resources, no destructive capabilities, and no financial implications. The context of sibling tools (apply, deploy, delete, create) confirms this is an informational/analytical tool.
From the tool's definition Tool name 'analyze_dependencies' and description 'Analyze resource dependencies' indicate a query/analysis operation that examines relationships between infrastructure resources without modifying, deleting, or executing deployments.
Attacks that exploit this kind of access
Analyze resource dependencies. 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 analyze_dependencies: 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.
analyze_dependencies 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 analyze_dependencies 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 analyze_dependencies. 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.
analyze_dependencies 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 →