Search across all log fields including textPayload, jsonPayload, protoPayload, labels, HTTP requests, and metadata. Provides maximum context.
AI agents call gcp-logging-search-comprehensive to retrieve information from Google Cloud MCP Server 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 log data across multiple fields without any side effects or state changes. While searching comprehensive logs could expose sensitive information in a multi-tenant GCP environment (hence medium severity rather than low), the core function is read-only retrieval. An AI agent misusing this would be confined to information disclosure rather than data modification or destruction.
From the tool's definition Tool name includes 'search' and description states it 'Search[es] across all log fields' with 'Provides maximum context' — purely a query operation with no modification, deletion, or execution capability.
Documented attack patterns abuse exactly the kind of access gcp-logging-search-comprehensive gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Google Cloud MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for gcp-logging-search-comprehensive:
{
"version": "1",
"default": "deny",
"tools": {
"gcp-logging-search-comprehensive": {}
}
}gcp-logging-search-comprehensive is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Search across all log fields including textPayload, jsonPayload, protoPayload, labels, HTTP requests, and metadata. Provides maximum context. It is categorised as a Read tool in the Google Cloud MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Google Cloud MCP Server MCP server in PolicyLayer and add a rule for gcp-logging-search-comprehensive: 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 Google Cloud MCP Server. Nothing to install.
gcp-logging-search-comprehensive 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-logging-search-comprehensive 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-logging-search-comprehensive. 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-logging-search-comprehensive is provided by the Google Cloud MCP Server MCP server (krzko/google-cloud-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Google Cloud MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
40 Google Cloud MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.