run_graphify
Generate a knowledge graph from a folder of code, docs, papers, or images.
This record as markdown: /tools/io-github-homenshum-nodebench/run-graphify.md
What run_graphify does on Nodebench
AI agents invoke run_graphify to trigger actions in Nodebench. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why run_graphify is rated High
This tool executes a non-trivial operation (knowledge graph generation) over arbitrary inputs. While not destructive or financial, it runs code/algorithms whose resource consumption and output depend entirely on attacker-controlled arguments (folder path, file types, size). An AI agent could be tricked into running this against sensitive codebases or creating expensive graph computations.
From the tool's definition Tool name 'run_graphify' paired with description 'Generate a knowledge graph' indicates execution of a graph generation process.
Attacks that exploit this kind of access
The rule that runs run_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 run_graphify, this is the rule to start with:
run_graphify stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Nodebench, apply this rule, and every run_graphify call is checked against it from then on.
Questions about run_graphify
Generate a knowledge graph from a folder of code, docs, papers, or images. It is categorised as a Execute tool in the Nodebench MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Nodebench MCP server in PolicyLayer and add a rule for run_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.
run_graphify is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the run_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.
Set action: deny in the PolicyLayer policy for run_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.
run_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.
More on Nodebench, and thousands of servers like it.
Across the catalogue