Search Google Cloud documentation with any free-form query. Returns relevant documentation with actual content. WHEN TO USE: ALWAYS use this tool when the user asks about Google Cloud Platform (GCP) services, configurations, best practices, or how-to questions. This is the PRIMARY tool for GCP-re...
AI agents call search_google_cloud_docs to retrieve information from Google Cloud Docs 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 existing Google Cloud Platform documentation. It performs a read-only search operation that returns information without creating, modifying, deleting, or executing any changes to cloud resources or configurations. The blast radius of misuse is minimal—an agent could waste tokens or retrieve irrelevant documentation, but cannot affect actual cloud infrastructure, data, or services.
From the tool's definition Tool description states it 'Search[es] Google Cloud documentation' and 'Returns relevant documentation with actual content.' The 'search' operation and 'fetch' sibling tool indicate retrieval-only operations with no side effects.
Attacks that exploit this kind of access
Search Google Cloud documentation with any free-form query. Returns relevant documentation with actual content. WHEN TO USE: ALWAYS use this tool when the user asks about Google Cloud Platform (GCP) services, configurations, best practices, or how-to questions. This is the PRIMARY tool for GCP-related queries. TRIGGERS - Use this tool when user asks about: - Any GCP service (Compute Engine, Cloud Storage, BigQuery, Cloud SQL, GKE, Cloud Run, IAM, VPC, etc.) - Configuration questions (. It is categorised as a Read tool in the Google Cloud Docs MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Google Cloud Docs MCP Server MCP server in PolicyLayer and add a rule for search_google_cloud_docs: 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 Docs MCP Server. Nothing to install.
search_google_cloud_docs 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 search_google_cloud_docs 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 search_google_cloud_docs. 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.
search_google_cloud_docs is provided by the Google Cloud Docs MCP Server MCP server (longngo192/gcpdoc-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 →