enrich_person

Trigger enrichment for a person — professional info, social profiles.

SERVERStarfield SOURCE@adrata/starfield-mcp

Low RISK CLASS

Category Read

Parameters 11 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/adrata-starfield-mcp/enrich-person.md

WHAT IT DOES

What enrich_person does on Starfield

AI agents call enrich_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
`personId`	string	Yes

Parameters from the server's own tool schema.

RISK

Why enrich_person is rated Low

Even though enrich_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

RECOMMENDED RULE

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

enrich_person Allowed

enrich_person 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": {
    "enrich_person": {}
  }
}

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

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

FAQ

Questions about enrich_person

What does the enrich_person tool do? +

Trigger enrichment for a person — professional info, social profiles. It is categorised as a Read tool in the Starfield MCP Server, which means it retrieves data without modifying state.

What parameters does enrich_person accept? +

enrich_person accepts 1 parameter: personId. Required: personId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on enrich_person? +

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

What risk level is enrich_person? +

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

Can I rate-limit enrich_person? +

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

How do I block enrich_person completely? +

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

What MCP server provides enrich_person? +

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

KEEP EXPLORING

More on Starfield, and thousands of servers like it.

This server

All 233 Starfield tools →

Across the catalogue

The MCP Attack Database →

Guides

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