Fetch and extract readable content from any URL. GitHub URLs are fetched via the GitHub API; all others go through a fetch cascade: Firecrawl → Crawl4AI → raw HTTP. Returns clean markdown where possible. Content truncated to 8000 characters. Results cached for 24 hours. Blocked domains are refused.
AI agents call fetch_url 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 is clearly a Read operation: it retrieves and queries data from URLs without creating, modifying, or deleting anything. Severity is medium rather than low because fetching arbitrary URLs could expose sensitive information (e.g., internal services, credentials in error pages, or private documents) if an AI agent is compromised or misdirected, and caching behavior could leak data across sessions.
From the tool's definition Tool description states it 'Fetch and extract readable content from any URL' and 'Returns clean markdown' — pure data retrieval with no modification, deletion, or execution of arbitrary code.
Documented attack patterns abuse exactly the kind of access fetch_url 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 fetch_url:
{
"version": "1",
"default": "deny",
"tools": {
"fetch_url": {}
}
}fetch_url 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.
Fetch and extract readable content from any URL. GitHub URLs are fetched via the GitHub API; all others go through a fetch cascade: Firecrawl → Crawl4AI → raw HTTP. Returns clean markdown where possible. Content truncated to 8000 characters. Results cached for 24 hours. Blocked domains are refused. 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 fetch_url: 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.
fetch_url 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 fetch_url 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 fetch_url. 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.
fetch_url 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.