Search the web using SearXNG. Returns relevant web pages with titles, URLs, and content snippets. Supports filtering and multiple concurrent searches.
AI agents call web_search to retrieve information from SearXNG MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
web_search performs read-only queries against a SearXNG instance and returns information (titles, URLs, snippets). It has no side effects on data or systems—it merely retrieves and presents search results. Even with filtering options (domain exclusion, time-range limits), these are query parameters that don't alter state.
From the tool's definition Tool description states it "Search the web using SearXNG. Returns relevant web pages with titles, URLs, and content snippets." This is a retrieval operation with no modification, deletion, execution of code, or financial transactions.
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 SearXNG MCP Server, 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 using SearXNG. Returns relevant web pages with titles, URLs, and content snippets. Supports filtering and multiple concurrent searches. It is categorised as a Read tool in the SearXNG MCP Server MCP Server, which means it retrieves data without modifying state.
Register the SearXNG MCP Server 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 SearXNG MCP Server. 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 SearXNG MCP Server MCP server (pascalrjt/searxng-websearch-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from SearXNG 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.
3 SearXNG MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.