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 Ai Scrapeless without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information through search without modifying, executing arbitrary commands, or causing irreversible changes. It is a passive data retrieval mechanism similar to a search API. The 'universal information search' and 'comparative analysis' functions are lookup operations with no side effects.
From the tool's definition Tool description states 'Retrieves any data information' and 'Explanatory queries', with context showing sibling tools are browser automation (click, screenshot, goto, etc.). google_search is a read-only query operation.
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 Ai Scrapeless MCP Server, which means it retrieves data without modifying state.
Register the Scrapeless Ai 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 Ai 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 Ai Scrapeless MCP server (@iflow-mcp/scrapeless-ai-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 →