List all resources in the infrastructure
AI agents call list_resources 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 displays infrastructure resource information without side effects. It performs a read-only operation analogous to 'list' or 'get' operations. The context of sibling tools (which include destructive operations like delete_resource, execute operations like deploy_resources, and write operations like create_resource) further confirms this tool's read-only nature.
From the tool's definition Tool name 'list_resources' and description 'List all resources in the infrastructure' indicate a query/retrieval operation with no data modification, deletion, or execution of external operations.
Attacks that exploit this kind of access
List all resources in the infrastructure. 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_resources: 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_resources 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_resources 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_resources. 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_resources 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 →