Clear the search results cache. Useful when you need fresh results or to free up memory.
AI agents call clear_cache to permanently remove resources in SearXNG MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Clearing a cache is an irreversible deletion of stored data (cached search results). While the blast radius is low (only cached results are lost, no permanent data loss since results can be re-fetched), the action cannot be undone and qualifies as Destructive. Severity is low because the worst case is having to re-fetch search results.
From the tool's definition 'Clear the search results cache' — irreversibly removes cached search results data
Documented attack patterns abuse exactly the kind of access clear_cache 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 clear_cache:
{
"version": "1",
"default": "deny",
"hide": [
"clear_cache"
]
}clear_cache disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Clear the search results cache. Useful when you need fresh results or to free up memory. It is categorised as a Destructive tool in the SearXNG MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the SearXNG MCP Server MCP server in PolicyLayer and add a rule for clear_cache: 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.
clear_cache is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the clear_cache 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 clear_cache. 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.
clear_cache 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.