AI agents call query_knowledge_graph 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.
Knowledge graph queries typically retrieve or traverse existing data without modifying state. The sibling tools (search, perform_rag_query, scrape_urls) all perform read operations on indexed/stored data. While the empty description creates some uncertainty, the name pattern and server purpose indicate this is a retrieval operation. No evidence of data mutation, deletion, code execution, or financial impact.
From the tool's definition Tool name 'query_knowledge_graph' and server context (web search, RAG, Supabase) suggest data retrieval from a knowledge graph. Description is empty, reducing specificity.
Documented attack patterns abuse exactly the kind of access query_knowledge_graph 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 query_knowledge_graph:
{
"version": "1",
"default": "deny",
"tools": {
"query_knowledge_graph": {}
}
}query_knowledge_graph is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
query_knowledge_graph. It is categorised as a Read tool in the Crawl4AI+SearXNG MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Crawl4AI+SearXNG MCP Server MCP server in PolicyLayer and add a rule for query_knowledge_graph: 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.
query_knowledge_graph 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 query_knowledge_graph 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 query_knowledge_graph. 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.
query_knowledge_graph 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.
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.