getEntityContextByName
Look up an entity context by its canonical name (exact match).
This record as markdown: /tools/io-github-homenshum-nodebench/getentitycontextbyname.md
What getEntityContextByName does on Nodebench
AI agents call getEntityContextByName 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 getEntityContextByName is rated Low
This tool performs a straightforward data lookup by name. It retrieves information without modifying, executing code, deleting, or creating anything. The operation is a pure read, returning context information for an entity. No destructive, financial, or execution capabilities are present.
From the tool's definition Tool name 'getEntityContextByName' and description 'Look up an entity context by its canonical name (exact match)' indicate a query/retrieval operation.
Attacks that exploit this kind of access
The rule that runs getEntityContextByName 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 getEntityContextByName, this is the rule to start with:
getEntityContextByName 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 getEntityContextByName call is checked against it from then on.
Questions about getEntityContextByName
Look up an entity context by its canonical name (exact match). 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 getEntityContextByName: 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.
getEntityContextByName 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 getEntityContextByName 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 getEntityContextByName. 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.
getEntityContextByName 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