nodebench.get_entity_dossier
Get a sourced public entity dossier from NodeBench public research memory by entity_key or name/type.
This record as markdown: /tools/io-github-homenshum-nodebench/nodebench.get-entity-dossier.md
What nodebench.get_entity_dossier does on Nodebench
AI agents call nodebench.get_entity_dossier 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 nodebench.get_entity_dossier is rated Low
This tool retrieves existing dossier data from a public research database. There are no side effects, no data modification, no code execution, and no destructive operations. The data source is public, limiting exposure risk. The blast radius of misuse is minimal — an AI agent could only retrieve information it shouldn't have access to, not modify systems or cause financial harm.
From the tool's definition Tool description states 'Get a sourced public entity dossier' — the verb 'Get' and context of retrieving from 'public research memory' indicate read-only data retrieval with no modification or execution capability.
Attacks that exploit this kind of access
The rule that runs nodebench.get_entity_dossier 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 nodebench.get_entity_dossier, this is the rule to start with:
nodebench.get_entity_dossier 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 nodebench.get_entity_dossier call is checked against it from then on.
Questions about nodebench.get_entity_dossier
Get a sourced public entity dossier from NodeBench public research memory by entity_key or name/type. 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 nodebench.get_entity_dossier: 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.
nodebench.get_entity_dossier 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 nodebench.get_entity_dossier 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 nodebench.get_entity_dossier. 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.
nodebench.get_entity_dossier 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