AI agents call search to retrieve information from Scrapegraph without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The name 'search' combined with the context of a web scraping and data extraction server suggests this tool queries or retrieves information without modifying data. While the empty description reduces confidence slightly, the tool's placement among read-like operations (extract, history, monitor_activity) and the server's overall purpose (data scraping) indicates this is a Read operation.
From the tool's definition Tool named 'search' on a scraping/crawling MCP server (ScrapeGraphAI); sibling tools include crawl_start, crawl_get_status, extract, and history, indicating data retrieval capabilities. No description provided.
Documented attack patterns abuse exactly the kind of access search gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Scrapegraph, and nothing reaches the server without passing your rules. This is the rule we recommend for search:
{
"version": "1",
"default": "deny",
"tools": {
"search": {}
}
}search is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
search. It is categorised as a Read tool in the Scrapegraph MCP Server, which means it retrieves data without modifying state.
Register the Scrapegraph MCP server in PolicyLayer and add a rule for 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 Scrapegraph. Nothing to install.
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 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 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.
search is provided by the Scrapegraph MCP server (ScrapeGraphAI/scrapegraph-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Scrapegraph, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
17 Scrapegraph tools catalogued and risk-classified — across an index of 43,000+ MCP servers.