searxng_list_engines

List the search engines configured in this SearXNG instance

SERVERCrow SOURCEkh0pper/crow

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/kh0pper-crow/searxng-list-engines.md

WHAT IT DOES

What searxng_list_engines does on Crow

AI agents call searxng_list_engines to retrieve information from Crow without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why searxng_list_engines is rated Low

This tool retrieves and enumerates search engine configuration from a SearXNG instance. It performs a read-only query with no side effects, no data modification, and no execution of external operations. The blast radius if misused by an AI agent is minimal—an agent could only learn what search engines are available, which is informational and non-destructive.

From the tool's definition Tool name contains 'list' and description states 'List the search engines configured' — a query operation that retrieves configuration data without modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs searxng_list_engines safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Crow, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For searxng_list_engines, this is the rule to start with:

searxng_list_engines Allowed

searxng_list_engines is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "searxng_list_engines": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Crow, apply this rule, and every searxng_list_engines call is checked against it from then on.

FAQ

Questions about searxng_list_engines

What does the searxng_list_engines tool do? +

List the search engines configured in this SearXNG instance. It is categorised as a Read tool in the Crow MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on searxng_list_engines? +

Register the Crow MCP server in PolicyLayer and add a rule for searxng_list_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 Crow. Nothing to install.

What risk level is searxng_list_engines? +

searxng_list_engines is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit searxng_list_engines? +

Yes. Add a rate_limit block to the searxng_list_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.

How do I block searxng_list_engines completely? +

Set action: deny in the PolicyLayer policy for searxng_list_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.

What MCP server provides searxng_list_engines? +

searxng_list_engines is provided by the Crow MCP server (kh0pper/crow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Crow, and thousands of servers like it.

This server

All 587 Crow tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →