enrich_entity
Enrich an entity (company, person, theme, market) with structured intelligence.
This record as markdown: /tools/io-github-homenshum-nodebench/enrich-entity.md
What enrich_entity does on Nodebench
AI agents call enrich_entity 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 enrich_entity is rated Low
The term 'enrich' typically means to supplement or augment existing data with additional information. This is fundamentally a Read operation that retrieves and structures intelligence about entities (companies, persons, themes, markets) from available sources. While enrichment could involve external API calls or data aggregation, no write, delete, execute, or financial operation occurs.
From the tool's definition Tool description states 'Enrich an entity...with structured intelligence' — a retrieval and aggregation operation that adds context by querying external data sources without modifying the underlying entity itself.
Attacks that exploit this kind of access
The rule that runs enrich_entity 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 enrich_entity, this is the rule to start with:
enrich_entity 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 enrich_entity call is checked against it from then on.
Questions about enrich_entity
Enrich an entity (company, person, theme, market) with structured intelligence. 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 enrich_entity: 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.
enrich_entity 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 enrich_entity 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 enrich_entity. 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.
enrich_entity 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