searxng_search
AI agents call searxng_search to retrieve information from MCP Developer Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Search tools retrieve data without modifying, deleting, or executing operations. Even if the search could theoretically access sensitive documentation, the primary function is read-only query. The low severity reflects that misuse would yield information exposure rather than destructive or financial harm. Confidence is moderate (0.85) due to empty description, but the naming and server context are clear indicators.
From the tool's definition Tool name 'searxng_search' indicates a search operation. SearXNG is a privacy-respecting metasearch engine. The server context describes 'documentation lookup' as a core function.
Attacks that exploit this kind of access
searxng_search. It is categorised as a Read tool in the MCP Developer Server MCP Server, which means it retrieves data without modifying state.
Register the MCP Developer Server MCP server in PolicyLayer and add a rule for searxng_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 MCP Developer Server. Nothing to install.
searxng_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 searxng_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 searxng_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.
searxng_search is provided by the MCP Developer Server MCP server (ra86-dev/mcpdev-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →