rank_people_by_icp
Rank a set of people by fit to the workspace ICP profile (title/persona match blended with company firmographics). Use after importing a list of people (e.g. LinkedIn post engagers) to surface the best-fit contacts first.
This record as markdown: /tools/adrata-starfield-mcp/rank-people-by-icp.md
What rank_people_by_icp does on Starfield
AI agents use rank_people_by_icp to create or update resources in Starfield, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Starfield environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
topN | number | — | |
minScore | number | — | |
personIds | array | Yes |
Parameters from the server's own tool schema.
Why rank_people_by_icp is rated Medium
An AI agent can call rank_people_by_icp faster than any human can review: one bad instruction and it creates or modifies resources in Starfield by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs rank_people_by_icp 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 rank_people_by_icp, this is the rule to start with:
rank_people_by_icp stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 rank_people_by_icp call is checked against it from then on.
Questions about rank_people_by_icp
Rank a set of people by fit to the workspace ICP profile (title/persona match blended with company firmographics). Use after importing a list of people (e.g. LinkedIn post engagers) to surface the best-fit contacts first. It is categorised as a Write tool in the Starfield MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
rank_people_by_icp accepts 3 parameters: topN, minScore, personIds. Required: personIds. 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 rank_people_by_icp: 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.
rank_people_by_icp is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the rank_people_by_icp 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 rank_people_by_icp. 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.
rank_people_by_icp 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