getThreadsByEntity
Get all narrative threads associated with a specific entity (company or person name).
This record as markdown: /tools/io-github-homenshum-nodebench/getthreadsbyentity.md
What getThreadsByEntity does on Nodebench
AI agents call getThreadsByEntity 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 getThreadsByEntity is rated Low
This tool queries and retrieves narrative threads linked to entities (companies or persons) without creating, modifying, deleting, or executing any operations. It is a straightforward data retrieval function with no side effects, fitting the Read category. The low severity reflects minimal risk from misuse—retrieving existing narrative threads poses no damage or critical harm.
From the tool's definition Tool name 'getThreadsByEntity' and description 'Get all narrative threads associated with a specific entity' indicate a retrieval operation with no modification or deletion of data.
Attacks that exploit this kind of access
The rule that runs getThreadsByEntity 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 getThreadsByEntity, this is the rule to start with:
getThreadsByEntity 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 getThreadsByEntity call is checked against it from then on.
Questions about getThreadsByEntity
Get all narrative threads associated with a specific entity (company or person name). 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 getThreadsByEntity: 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.
getThreadsByEntity 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 getThreadsByEntity 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 getThreadsByEntity. 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.
getThreadsByEntity 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