This record as markdown: /tools/io-github-homenshum-nodebench/getentity.md
What getEntity does on Nodebench
AI agents call getEntity 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 getEntity is rated Low
This tool retrieves data by key lookup and returns an entity. The operation is read-only with no side effects, no irreversible actions, and no code execution or financial impact. The minimal severity reflects that data retrieval has limited blast radius unless the retrieved data itself contains sensitive information, but the tool's core function is purely informational.
From the tool's definition Tool description states 'Get a canonical entity by its entityKey' - the verb 'Get' indicates a retrieval operation with no modification or deletion.
Attacks that exploit this kind of access
The rule that runs getEntity 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 getEntity, this is the rule to start with:
getEntity 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 getEntity call is checked against it from then on.
Questions about getEntity
Get a canonical entity by its entityKey. 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 getEntity: 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.
getEntity 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 getEntity 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 getEntity. 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.
getEntity 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