enroll_contacts
Enroll contacts into a sequence. Contacts will begin receiving sequence emails according to the step schedule. Enterprise only.
This record as markdown: /tools/adrata-starfield-mcp/enroll-contacts.md
What enroll_contacts does on Starfield
AI agents call enroll_contacts 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 |
|---|---|---|---|
mailboxId | string | — | Override mailbox ID for these enrollments |
contactIds | array | Yes | Array of person/contact IDs to enroll |
sequenceId | string | Yes | Sequence ID to enroll contacts into |
Parameters from the server's own tool schema.
Why enroll_contacts is rated Low
Even though enroll_contacts 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 enroll_contacts 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 enroll_contacts, this is the rule to start with:
enroll_contacts 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 enroll_contacts call is checked against it from then on.
Questions about enroll_contacts
Enroll contacts into a sequence. Contacts will begin receiving sequence emails according to the step schedule. Enterprise only. It is categorised as a Read tool in the Starfield MCP Server, which means it retrieves data without modifying state.
enroll_contacts accepts 3 parameters: mailboxId, contactIds, sequenceId. Required: contactIds, sequenceId. 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 enroll_contacts: 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.
enroll_contacts 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 enroll_contacts 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 enroll_contacts. 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.
enroll_contacts 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