create_sequence
Create a new multi-step email sequence. Define the name and optionally include initial steps. Steps specify delay, subject, and body template. Enterprise only.
This record as markdown: /tools/adrata-starfield-mcp/create-sequence.md
What create_sequence does on Starfield
AI agents use create_sequence 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 |
|---|---|---|---|
name | string | Yes | Sequence name (e.g. "Cold Outreach Q2 2026") |
steps | array | — | Initial sequence steps. Can also add steps later with add_sequence_step. |
mailboxId | string | — | Default mailbox ID to send from |
description | string | — | Sequence description |
Parameters from the server's own tool schema.
Why create_sequence is rated Medium
An AI agent can call create_sequence 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 (steps[].body)
Attacks that exploit this kind of access
The rule that runs create_sequence 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 create_sequence, this is the rule to start with:
create_sequence 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 create_sequence call is checked against it from then on.
Questions about create_sequence
Create a new multi-step email sequence. Define the name and optionally include initial steps. Steps specify delay, subject, and body template. 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.
create_sequence accepts 4 parameters: name, steps, mailboxId, description. 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 create_sequence: 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.
create_sequence 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 create_sequence 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 create_sequence. 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.
create_sequence 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