Search the web, rerank results, then fetch the full content of the top result(s). GitHub URLs are fetched via the GitHub API; all others go through a fetch cascade: Firecrawl → Crawl4AI → raw HTTP. Results and fetched pages are cached. Blocked domains are filtered. Returns the result list plus cl...
AI agents call search_and_fetch to retrieve information from Searxng without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries data from the web without creating, modifying, deleting, or executing code. It aggregates public web content and returns it in processed form (markdown). No side effects occur on the user's system or data. The caching mechanism is a performance optimization, not a data modification operation. Confidence is high due to clear read-only semantics in the description.
From the tool's definition Tool performs search, reranking, and content fetching operations. Description explicitly states it 'Search the web, rerank results, then fetch the full content' and 'Returns the result list plus clean markdown of the fetched pages.' All verbs indicate…
Documented attack patterns abuse exactly the kind of access search_and_fetch gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Searxng, and nothing reaches the server without passing your rules. This is the rule we recommend for search_and_fetch:
{
"version": "1",
"default": "deny",
"tools": {
"search_and_fetch": {}
}
}search_and_fetch 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, rerank results, then fetch the full content of the top result(s). GitHub URLs are fetched via the GitHub API; all others go through a fetch cascade: Firecrawl → Crawl4AI → raw HTTP. Results and fetched pages are cached. Blocked domains are filtered. Returns the result list plus clean markdown of the fetched pages. It is categorised as a Read tool in the Searxng MCP Server, which means it retrieves data without modifying state.
Register the Searxng MCP server in PolicyLayer and add a rule for search_and_fetch: 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. Nothing to install.
search_and_fetch 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_and_fetch 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_and_fetch. 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_and_fetch is provided by the Searxng MCP server (tadmstr/searxng-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Searxng, 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.
6 Searxng tools catalogued and risk-classified — across an index of 43,000+ MCP servers.