Executes multiple Google search queries in parallel. Returns a combined list of results for each query. Highly efficient for broad research across multiple related topics.
AI agents call multi_search to retrieve information from Web-curl MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool fetches and returns search query results from Google. It performs information retrieval operations only—no data creation, modification, deletion, code execution, or financial transactions. The worst-case misuse is retrieving sensitive information already public via search, which is a read-only operation with limited blast radius.
From the tool's definition Tool description states it 'Executes multiple Google search queries' and 'Returns a combined list of results'. The verb 'Returns' and the focus on retrieval of search results indicate data retrieval with no side effects.
Documented attack patterns abuse exactly the kind of access multi_search gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Web-curl MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for multi_search:
{
"version": "1",
"default": "deny",
"tools": {
"multi_search": {}
}
}multi_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.
Executes multiple Google search queries in parallel. Returns a combined list of results for each query. Highly efficient for broad research across multiple related topics. It is categorised as a Read tool in the Web-curl MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Web-curl MCP Server MCP server in PolicyLayer and add a rule for multi_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 Web-curl MCP Server. Nothing to install.
multi_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 multi_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 multi_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.
multi_search is provided by the Web-curl MCP Server MCP server (rayss868/mcp-web-curl). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Web-curl MCP Server, 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.
7 Web-curl MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.