Get search suggestions from SearXNG.
AI agents call searxng_suggestions 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.
This tool retrieves autocomplete or suggestion data from SearXNG, a metasearch engine. It is a pure read operation with no side effects—it does not create, modify, execute, or delete anything. The search suggestions are informational only, making this a straightforward Read category tool with low severity since misuse would only surface search suggestions without operational impact.
From the tool's definition Tool name 'searxng_suggestions' and description 'Get search suggestions from SearXNG' indicate a retrieval operation that queries a search engine for suggestions without modifying, executing, or deleting any data.
Attacks that exploit this kind of access
Get search suggestions from SearXNG. 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_suggestions: 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_suggestions 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_suggestions 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_suggestions. 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_suggestions is provided by the MCP Developer Server MCP server (ra86-dev/mcpdockershell). 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 →