Search Google and return relevant results from the web. Results include titles, snippets, and URLs.
AI agents call google_search to retrieve information from Simple Google Search without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
google_search performs a read-only query operation that retrieves publicly available search results. It has no capability to modify, delete, or execute actions on data or external systems. The only potential concern is that search queries could be used to gather reconnaissance information, but this is inherent to any search tool and does not elevate the risk category.
From the tool's definition Tool description states it 'Search Google and return relevant results from the web. Results include titles, snippets, and URLs.' This is a retrieval operation with no side effects on any system.
Attacks that exploit this kind of access
Search Google and return relevant results from the web. Results include titles, snippets, and URLs. It is categorised as a Read tool in the Simple Google Search MCP Server, which means it retrieves data without modifying state.
Register the Simple Google Search MCP server in PolicyLayer and add a rule for google_search: 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 Simple Google Search. Nothing to install.
google_search 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 google_search 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 google_search. 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.
google_search is provided by the Simple Google Search MCP server (xrayzen/simple-google-search-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 →