entity_lookup
Quick intelligence on any company, person, or topic. Type a name, get structured facts, signals, and suggested next tools. The simplest entry point into NodeBench — no setup needed.
This record as markdown: /tools/io-github-homenshum-nodebench/entity-lookup.md
What entity_lookup does on Nodebench
AI agents call entity_lookup 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 entity_lookup is rated Low
This tool is clearly designed for data retrieval and enrichment - looking up and returning information about companies, persons, or topics. It has no capability to modify, delete, or execute operations based on the description provided. The mention of 'suggested next tools' indicates it serves as a discovery/navigation aid rather than an action tool. This is a straightforward Read operation with minimal blast radius.
From the tool's definition Tool performs a 'lookup' operation returning 'structured facts and signals' with 'no setup needed' - this is a query/retrieval action with no indication of modifications, deletions, or execution of code.
Attacks that exploit this kind of access
The rule that runs entity_lookup 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 entity_lookup, this is the rule to start with:
entity_lookup 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 entity_lookup call is checked against it from then on.
Questions about entity_lookup
Quick intelligence on any company, person, or topic. Type a name, get structured facts, signals, and suggested next tools. The simplest entry point into NodeBench — no setup needed. 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 entity_lookup: 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.
entity_lookup 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 entity_lookup 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 entity_lookup. 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.
entity_lookup 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