Get list of available search engines from SearXNG instance.
AI agents call searxng_get_engines 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 queries and returns metadata about available search engines from a SearXNG instance. It performs a read-only operation that retrieves configuration or status information without modifying, creating, or deleting any data. The low severity reflects minimal blast radius—an agent cannot misuse this to cause harm beyond potentially gaining visibility into the search engine landscape.
From the tool's definition Tool name 'searxng_get_engines' and description 'Get list of available search engines' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
Get list of available search engines from SearXNG instance. 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_get_engines: 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_get_engines 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_get_engines 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_get_engines. 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_get_engines 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 →