get_entity_graph_summary
Get a summary of the knowledge graph: entity counts by type, edge counts by relation, recent additions.
This record as markdown: /tools/io-github-homenshum-nodebench/get-entity-graph-summary.md
What get_entity_graph_summary does on Nodebench
AI agents call get_entity_graph_summary 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 get_entity_graph_summary is rated Low
This tool retrieves and queries data from a knowledge graph without creating, modifying, deleting, or executing any operations. It is a pure information retrieval operation with no side effects. The blast radius of misuse is minimal—an agent could only learn structure and statistics about existing data. This maps clearly to the 'Read' category.
From the tool's definition The tool description explicitly states it 'Get[s] a summary' of a knowledge graph, reporting 'entity counts by type, edge counts by relation, recent additions.' These are all read-only query operations that retrieve existing data without modification.
Attacks that exploit this kind of access
The rule that runs get_entity_graph_summary 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 get_entity_graph_summary, this is the rule to start with:
get_entity_graph_summary 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 get_entity_graph_summary call is checked against it from then on.
Questions about get_entity_graph_summary
Get a summary of the knowledge graph: entity counts by type, edge counts by relation, recent additions. 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 get_entity_graph_summary: 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.
get_entity_graph_summary 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 get_entity_graph_summary 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 get_entity_graph_summary. 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.
get_entity_graph_summary 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