List common GCP monitored resource types for log filtering.
AI agents call gcp_list_log_resource_types to retrieve information from GCP MCP Log Diagnostics without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a simple enumeration/lookup tool that retrieves metadata about GCP resource types available for filtering logs. It performs no writes, deletes, or code execution—purely informational data retrieval with minimal blast radius if misused (would return static reference data about resource type names).
From the tool's definition Tool name and description indicate listing/retrieval of monitored resource types: 'List common GCP monitored resource types' with no mutation, deletion, or execution capability.
Attacks that exploit this kind of access
List common GCP monitored resource types for log filtering. It is categorised as a Read tool in the GCP MCP Log Diagnostics MCP Server, which means it retrieves data without modifying state.
Register the GCP MCP Log Diagnostics MCP server in PolicyLayer and add a rule for gcp_list_log_resource_types: 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 GCP MCP Log Diagnostics. Nothing to install.
gcp_list_log_resource_types 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 gcp_list_log_resource_types 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 gcp_list_log_resource_types. 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.
gcp_list_log_resource_types is provided by the GCP MCP Log Diagnostics MCP server (kanhaiworld/gcp_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 →