Search Google for a query
AI agents call search_google to retrieve information from Mcp Webresearch without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
query | string | Yes | Search query |
Parameters from the server's own tool schema.
This tool performs a read-only query against Google's search engine. It retrieves search results based on user input but does not create, modify, delete, or execute any operations on systems or data. The sibling tools (take_screenshot, visit_page) are also browser-based read operations, consistent with a web research server focused on information retrieval.
From the tool's definition Tool name 'search_google' and description 'Search Google for a query' indicate a search operation that retrieves information without modifying data or executing code.
Risk signalsAccepts freeform code/query input (query)
Attacks that exploit this kind of access
Search Google for a query. It is categorised as a Read tool in the Mcp Webresearch MCP Server, which means it retrieves data without modifying state.
search_google accepts 1 parameter: query. Required: query. The full parameter table on this page comes from the server's own tool schema.
Register the Mcp Webresearch MCP server in PolicyLayer and add a rule for search_google: 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 Mcp Webresearch. Nothing to install.
search_google 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 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. 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 is provided by the Mcp Webresearch MCP server (@mzxrai/mcp-webresearch). 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 →