AI agents call web_search to retrieve information from Search without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Web search retrieves publicly available information without creating, modifying, deleting, or executing operations. This is a classic Read operation. Severity is low because the tool cannot alter data, move money, or execute code; misuse by an AI agent would at worst return irrelevant results, not cause harm.
From the tool's definition Tool name is 'web_search' and description states 'Search the web for information' — a purely informational retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access web_search gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Search, and nothing reaches the server without passing your rules. This is the rule we recommend for web_search:
{
"version": "1",
"default": "deny",
"tools": {
"web_search": {}
}
}web_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 the web for information. It is categorised as a Read tool in the Search MCP Server, which means it retrieves data without modifying state.
Register the Search MCP server in PolicyLayer and add a rule for web_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 Search. Nothing to install.
web_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 web_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 web_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.
web_search is provided by the Search MCP server (@agent-infra/mcp-server-search). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Search, 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.
36 Search tools catalogued and risk-classified — across an index of 43,000+ MCP servers.