query_graphify

Query an existing graphify knowledge graph. Find nodes by label, explore connections,

SERVERNodebench SOURCEnodebench-mcp

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-homenshum-nodebench/query-graphify.md

WHAT IT DOES

What query_graphify does on Nodebench

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

RISK

Why query_graphify is rated Low

The tool performs read-only operations: querying an existing knowledge graph, finding nodes, and exploring connections. These are information retrieval actions with no side effects, data modification, code execution, or destructive capabilities. The 'query' verb and emphasis on 'find' and 'explore' indicate passive data access only.

From the tool's definition Tool description explicitly states 'Query an existing graphify knowledge graph. Find nodes by label, explore connections' — pure querying and exploration with no mutation or execution capabilities mentioned.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs query_graphify safely

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

query_graphify Allowed

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

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

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

FAQ

Questions about query_graphify

What does the query_graphify tool do? +

Query an existing graphify knowledge graph. Find nodes by label, explore connections,. It is categorised as a Read tool in the Nodebench MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on query_graphify? +

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

What risk level is query_graphify? +

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

Can I rate-limit query_graphify? +

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

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

query_graphify is provided by the Nodebench MCP server (nodebench-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Nodebench, and thousands of servers like it.

This server

All 824 Nodebench 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 →