getPersonProfile
Get executive/person profile with employment history, board roles, and credibility score.
This record as markdown: /tools/io-github-homenshum-nodebench/getpersonprofile.md
What getPersonProfile does on Nodebench
AI agents call getPersonProfile 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 getPersonProfile is rated Low
This is a data retrieval operation that queries and returns information about individuals. While it gathers potentially sensitive PII (employment history, roles) that could be misused for social engineering, impersonation, or harassment, the tool itself performs no destructive, financial, or executable actions.
From the tool's definition Tool retrieves person profile data including employment history, board roles, and credibility score. The description uses 'Get' (retrieve) verb with no mention of modifications, deletions, or side effects.
Attacks that exploit this kind of access
The rule that runs getPersonProfile 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 getPersonProfile, this is the rule to start with:
getPersonProfile 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 getPersonProfile call is checked against it from then on.
Questions about getPersonProfile
Get executive/person profile with employment history, board roles, and credibility score. 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 getPersonProfile: 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.
getPersonProfile 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 getPersonProfile 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 getPersonProfile. 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.
getPersonProfile 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