Search Google and return structured results as JSON. Each result includes title, URL, and snippet. Also returns top stories, knowledge graph, local results, news, images, and related searches depending on search type. Use when the user asks to search the web, find current information, or look som...
AI agents call search_google to retrieve information from Scavio without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a web search query and returns information. It retrieves data without modifying, deleting, or executing any operations. The blast radius of misuse is minimal—an agent could search for irrelevant or sensitive topics, but cannot cause data loss or execute harmful operations. This is a straightforward Read operation.
From the tool's definition Tool description states it "Search[es] Google and return[s] structured results as JSON" with "title, URL, and snippet." No mention of creating, modifying, deleting, or executing operations. The verb 'search' and 'return' confirm retrieval without side effects.
Attacks that exploit this kind of access
Search Google and return structured results as JSON. Each result includes title, URL, and snippet. Also returns top stories, knowledge graph, local results, news, images, and related searches depending on search type. Use when the user asks to search the web, find current information, or look something up online. Returns 1 credit (light) or 2 credits (full). It is categorised as a Read tool in the Scavio MCP Server, which means it retrieves data without modifying state.
Register the Scavio 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 Scavio. 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 Scavio MCP server (@scavio/mcp-server). 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 →