nodebench.research_person
Run or reuse public-source person research, store verified public claims, and return a compact person dossier.
This record as markdown: /tools/io-github-homenshum-nodebench/nodebench.research-person.md
What nodebench.research_person does on Nodebench
AI agents call nodebench.research_person 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.research_person is rated Low
The tool retrieves and aggregates publicly available information about individuals and returns a dossier. While it 'stores' verified claims (a minor write side effect), the primary function is research/retrieval of public data. The severity is medium because aggregating personal data into a dossier can raise privacy concerns and could be misused for surveillance or profiling, even if sourced from public records.
From the tool's definition 'Run or reuse public-source person research, store verified public claims, and return a compact person dossier'
Attacks that exploit this kind of access
The rule that runs nodebench.research_person 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.research_person, this is the rule to start with:
nodebench.research_person 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.research_person call is checked against it from then on.
Questions about nodebench.research_person
Run or reuse public-source person research, store verified public claims, and return a compact person dossier. 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.research_person: 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.research_person 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.research_person 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.research_person. 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.research_person 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