getEntityContext

Get full entity context by ID, including all tracked metadata, relationships, funding data, and activity history.

SERVERNodebench SOURCEnodebench-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-homenshum-nodebench/getentitycontext.md

WHAT IT DOES

What getEntityContext does on Nodebench

AI agents call getEntityContext 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.

RISK

Why getEntityContext is rated Low

This tool queries and retrieves entity data (metadata, relationships, funding information, activity history) by ID. It performs no side effects, modifications, or irreversible actions. The 'Get' verb and retrieval-focused description clearly indicate a Read operation.

From the tool's definition 'Get full entity context by ID, including all tracked metadata, relationships, funding data, and activity history' — retrieves comprehensive data without modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs getEntityContext 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 getEntityContext, this is the rule to start with:

getEntityContext Allowed

getEntityContext is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "getEntityContext": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Nodebench, apply this rule, and every getEntityContext call is checked against it from then on.

FAQ

Questions about getEntityContext

What does the getEntityContext tool do? +

Get full entity context by ID, including all tracked metadata, relationships, funding data, and activity history. It is categorised as a Read tool in the Nodebench MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on getEntityContext? +

Register the Nodebench MCP server in PolicyLayer and add a rule for getEntityContext: 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.

What risk level is getEntityContext? +

getEntityContext is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit getEntityContext? +

Yes. Add a rate_limit block to the getEntityContext 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.

How do I block getEntityContext completely? +

Set action: deny in the PolicyLayer policy for getEntityContext. 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.

What MCP server provides getEntityContext? +

getEntityContext 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.

KEEP EXPLORING

More on Nodebench, and thousands of servers like it.

This server

All 824 Nodebench tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →