graphify_report
Get the GRAPH_REPORT.md analysis from a graphify run. Contains god nodes (most connected),
This record as markdown: /tools/io-github-homenshum-nodebench/graphify-report.md
What graphify_report does on Nodebench
AI agents call graphify_report 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.
Why graphify_report is rated Low
The tool fetches an existing report (GRAPH_REPORT.md) generated by a previous graphify run. This is a read-only retrieval operation with no side effects. Severity is low since it only reads analytical report data.
From the tool's definition 'Get the GRAPH_REPORT.md analysis from a graphify run' — retrieves/reads a report file
Attacks that exploit this kind of access
The rule that runs graphify_report 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 graphify_report, this is the rule to start with:
graphify_report is read-only, so it stays allowed. 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 graphify_report call is checked against it from then on.
Questions about graphify_report
Get the GRAPH_REPORT.md analysis from a graphify run. Contains god nodes (most connected),. It is categorised as a Read tool in the Nodebench MCP Server, which means it retrieves data without modifying state.
Register the Nodebench MCP server in PolicyLayer and add a rule for graphify_report: 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.
graphify_report 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 graphify_report 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 graphify_report. 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.
graphify_report 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.
This server
Across the catalogue