getEntityContextStats
Get aggregate statistics about the knowledge base: total entities, entities by type, coverage metrics.
This record as markdown: /tools/io-github-homenshum-nodebench/getentitycontextstats.md
What getEntityContextStats does on Nodebench
AI agents call getEntityContextStats 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 getEntityContextStats is rated Low
This tool queries and returns statistical information about a knowledge base without modifying, deleting, or executing any operations. It is a pure information retrieval function with minimal blast radius if misused by an agent—worst case would be repeated calls to gather statistics. No data modification, execution, financial impact, or destructive capability is present.
From the tool's definition Tool performs a retrieval/query operation to get 'aggregate statistics about the knowledge base: total entities, entities by type, coverage metrics'. Keywords like 'Get', 'statistics', and 'metrics' indicate read-only data retrieval with no side effects.
Attacks that exploit this kind of access
The rule that runs getEntityContextStats 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 getEntityContextStats, this is the rule to start with:
getEntityContextStats 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 getEntityContextStats call is checked against it from then on.
Questions about getEntityContextStats
Get aggregate statistics about the knowledge base: total entities, entities by type, coverage metrics. 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 getEntityContextStats: 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.
getEntityContextStats 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 getEntityContextStats 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 getEntityContextStats. 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.
getEntityContextStats 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