Low Risk

search

search

How to control search ↓

AI agents call search to retrieve information from Crawl4AI+SearXNG MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

The tool appears to perform web search queries without modifying, deleting, or executing arbitrary code. Even though the description is empty, the server's purpose (web search and RAG) and the presence of related read-only tools (search_code_examples, search_graphiti, get_available_sources) support classification as a retrieval operation with no side effects.

From the tool's definition Tool name 'search' combined with server's stated web search capability and sibling tools like 'perform_rag_query' and 'scrape_urls' indicate this retrieves query results. Empty description limits confidence but context strongly suggests read-only search.

Documented attack patterns abuse exactly the kind of access search gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Crawl4AI+SearXNG MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for search:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "search": {}
  }
}

search is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Crawl4AI+SearXNG MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the search tool do? +

search. It is categorised as a Read tool in the Crawl4AI+SearXNG MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search? +

Register the Crawl4AI+SearXNG MCP Server MCP server in PolicyLayer and add a rule for 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 Crawl4AI+SearXNG MCP Server. Nothing to install.

What risk level is search? +

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

Can I rate-limit search? +

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

How do I block search completely? +

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

What MCP server provides search? +

search is provided by the Crawl4AI+SearXNG MCP Server MCP server (tokidoo/crawl4ai-rag-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Crawl4AI+SearXNG MCP Server tool call.

Deterministic rules across all 10 Crawl4AI+SearXNG MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

10 Crawl4AI+SearXNG MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.