agentdb_graph-query

Unified graph traversal across the knowledge graph (ADR-130). Dispatches to the most capable backend: graph-node native for k-hop, sql.js CTE for fallback, HNSW cosine for semantic, ruflo-graph-intelligence PageRank for pagerank mode. Use when you need structured graph traversal beyond flat memor...

SERVERClaude Flow SOURCEclaude-flow

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/io-github-ruvnet-claude-flow/agentdb-graph-query.md

WHAT IT DOES

What agentdb_graph-query does on Claude Flow

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

RISK

Why agentdb_graph-query is rated Low

This tool performs traversal and querying of a knowledge graph across multiple backend engines. The description emphasizes retrieval ('traversal', 'search') with no mention of create, modify, delete, or execute capabilities.

From the tool's definition Tool is described as 'Unified graph traversal' and 'graph traversal' which retrieves structured data from a knowledge graph. Dispatches to backends for querying (k-hop, CTE, semantic, PageRank) without modification capabilities mentioned.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs agentdb_graph-query safely

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

agentdb_graph-query Allowed

agentdb_graph-query 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": {
    "agentdb_graph-query": {}
  }
}

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

The button opens the PolicyLayer dashboard: create your workspace, connect Claude Flow, apply this rule, and every agentdb_graph-query call is checked against it from then on.

FAQ

Questions about agentdb_graph-query

What does the agentdb_graph-query tool do? +

How do I enforce a policy on agentdb_graph-query? +

Register the Claude Flow MCP server in PolicyLayer and add a rule for agentdb_graph-query: 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 Claude Flow. Nothing to install.

What risk level is agentdb_graph-query? +

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

Can I rate-limit agentdb_graph-query? +

Yes. Add a rate_limit block to the agentdb_graph-query 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 agentdb_graph-query completely? +

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

agentdb_graph-query is provided by the Claude Flow MCP server (claude-flow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Claude Flow, and thousands of servers like it.

This server

All 496 Claude Flow tools →

Across the catalogue

claude_query on Claude Bridge → The MCP Attack Database →

Guides

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