add_sequence_step
Add a step to an existing sequence. Steps are executed in order with configurable delays between them. Enterprise only.
This record as markdown: /tools/adrata-starfield-mcp/add-sequence-step.md
What add_sequence_step does on Starfield
AI agents use add_sequence_step 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 |
|---|---|---|---|
body | string | Yes | Email body template (supports {{firstName}}, {{company}}, {{title}} variables) |
type | string | — | Step type: email (default), linkedin_view, linkedin_connect, call, manual |
order | number | Yes | Step order (1-based). Inserts at this position. |
subject | string | Yes | Email subject line (supports {{firstName}}, {{company}} variables) |
delayDays | number | Yes | Days to wait before sending this step (relative to previous step) |
sequenceId | string | Yes | Sequence ID to add the step to |
Parameters from the server's own tool schema.
Why add_sequence_step is rated Medium
An AI agent can call add_sequence_step 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.
Risk signalsAccepts raw HTML/template content (body)
Attacks that exploit this kind of access
The rule that runs add_sequence_step 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 add_sequence_step, this is the rule to start with:
add_sequence_step 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 add_sequence_step call is checked against it from then on.
Questions about add_sequence_step
Add a step to an existing sequence. Steps are executed in order with configurable delays between them. Enterprise only. 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.
add_sequence_step accepts 6 parameters: body, type, order, subject, delayDays, sequenceId. Required: body, order, subject, delayDays, 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 add_sequence_step: 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.
add_sequence_step 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 add_sequence_step 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 add_sequence_step. 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.
add_sequence_step 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