listEntityContexts
List all tracked entity contexts with pagination. Useful for browsing the knowledge base.
This record as markdown: /tools/io-github-homenshum-nodebench/listentitycontexts.md
What listEntityContexts does on Nodebench
AI agents call listEntityContexts 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 listEntityContexts is rated Low
This tool retrieves and lists information from a knowledge base without modifying, deleting, or executing operations. It is a straightforward data retrieval function with pagination support, typical of Read category tools. No side effects or external operations are triggered.
From the tool's definition Tool name 'listEntityContexts' and description 'List all tracked entity contexts with pagination' indicate a retrieval/query operation. The phrase 'Useful for browsing the knowledge base' confirms read-only access to existing data.
Attacks that exploit this kind of access
The rule that runs listEntityContexts 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 listEntityContexts, this is the rule to start with:
listEntityContexts 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 listEntityContexts call is checked against it from then on.
Questions about listEntityContexts
List all tracked entity contexts with pagination. Useful for browsing the knowledge base. 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 listEntityContexts: 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.
listEntityContexts 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 listEntityContexts 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 listEntityContexts. 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.
listEntityContexts 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