Universal Information Search Engine.Retrieves any data information; Explanatory queries (why, how).Comparative analysis requests
AI agents call google_search to retrieve information from Scrapeless without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs information retrieval through Google Search without side effects. It queries and returns data without creating, modifying, deleting, or executing operations. The sibling tools (browser_click, browser_goto, browser_screenshot) suggest a web scraping/browsing context, but google_search itself is purely a read operation that searches and returns information.
From the tool's definition Tool name 'google_search' and description explicitly states 'Retrieves any data information' and 'Explanatory queries'; no modification, deletion, or execution capabilities mentioned.
Attacks that exploit this kind of access
Universal Information Search Engine.Retrieves any data information; Explanatory queries (why, how).Comparative analysis requests. It is categorised as a Read tool in the Scrapeless MCP Server, which means it retrieves data without modifying state.
Register the Scrapeless 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 Scrapeless. 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 Scrapeless MCP server (scrapeless-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 →