AI agents call search_web 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 returns information without modifying, deleting, executing code, or committing financial transactions. The headless browser is used only for retrieval, not for clicking, submitting forms, or triggering actions. This is a standard Read operation. Confidence is high despite the empty tool description because the server description clearly establishes the scope and nature of the search functionality.
From the tool's definition Server description states the tool 'Enables web searching through Google, DuckDuckGo, and Bing' and returns 'structured results with titles, URLs, and snippets.' This is a retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access search_web 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 search_web:
{
"version": "1",
"default": "deny",
"tools": {
"search_web": {}
}
}search_web 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_web. 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 search_web: 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.
search_web 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_web 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_web. 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_web is provided by the Web Search MCP server (pranavms13/web-search-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Web Search MCP, 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.
4 Web Search MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.