find_person
Search for a professional using Claude's training data. Returns a structured profile with title, company, background, expertise, and sales context. Free tier — no API key needed. For verified contact info and buyer signals, upgrade to Pro.
This record as markdown: /tools/adrata-starfield-mcp/find-person.md
What find_person does on Starfield
AI agents call find_person to retrieve information from Starfield without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | Yes | Full name of the person to research (e.g. "Patrick Collison", "Jensen Huang") |
Parameters from the server's own tool schema.
Why find_person is rated Low
Even though find_person only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs find_person safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Starfield, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For find_person, this is the rule to start with:
find_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 Starfield, apply this rule, and every find_person call is checked against it from then on.
Questions about find_person
Search for a professional using Claude's training data. Returns a structured profile with title, company, background, expertise, and sales context. Free tier — no API key needed. For verified contact info and buyer signals, upgrade to Pro. It is categorised as a Read tool in the Starfield MCP Server, which means it retrieves data without modifying state.
find_person accepts 1 parameter: name. Required: name. The full parameter table on this page comes from the server's own tool schema.
Register the Starfield MCP server in PolicyLayer and add a rule for find_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 Starfield. Nothing to install.
find_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 find_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 find_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.
find_person is provided by the Starfield MCP server (@adrata/starfield-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Starfield, and thousands of servers like it.
This server
Across the catalogue