AI agents call web_search to retrieve information from Web Search MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Web search queries are fundamentally retrieval operations that return information without modifying, deleting, or executing anything. The tool searches public search engines and extracts content, which has no persistent side effects on external systems or data.
From the tool's definition Tool named 'web_search' is part of a 'Web Search MCP' server that 'converts results from Google, Bing, and DuckDuckGo into structured JSON or Markdown.' The sibling tool 'get_page_content' and server description confirm this is a data retrieval service with…
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 Web Search MCP, 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.
web_search. It is categorised as a Read tool in the Web Search MCP MCP Server, which means it retrieves data without modifying state.
Register the Web 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 Web Search MCP. 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 Web Search MCP server (uk0/web-search-fast). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 3 Web Search MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
3 Web Search MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.