Check SearXNG instance status and capabilities.
AI agents call searxng_status 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 performs a simple status check on a SearXNG search engine instance, returning metadata about its capabilities and health. It retrieves information without side effects, making it a Read operation. The low severity reflects minimal blast radius—an agent cannot misuse status queries to cause harm, though information disclosure is theoretically possible if sensitive status details are exposed.
From the tool's definition Tool name 'searxng_status' and description 'Check SearXNG instance status and capabilities' indicate a query operation that retrieves status information without modifying or executing any external operations.
Attacks that exploit this kind of access
Check SearXNG instance status and capabilities. 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_status: 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_status 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_status 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_status. 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_status 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 →