create_sequence
Creates a new sequence from a specific installed .sqpreset file without opening Premiere's New Sequence dialog. For footage-driven edits, prefer create_sequence_from_clips; for an empty copy of an existing sequence, use duplicate_sequence with clearContents=true.
This record as markdown: /tools/adobe-premiere-pro-mcp/create-sequence.md
What create_sequence does on Adobe Premiere Pro
AI agents use create_sequence to create or update resources in Adobe Premiere Pro, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Adobe Premiere Pro environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | Yes | The name for the new sequence |
presetPath | string | Yes | Absolute path to an installed Premiere .sqpreset sequence preset. Required so Premiere does not show the native New Sequence dialog. |
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 Adobe Premiere Pro by the hundred, each call as confident as the last.
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 Adobe Premiere Pro, 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 Adobe Premiere Pro, apply this rule, and every create_sequence call is checked against it from then on.
Questions about create_sequence
Creates a new sequence from a specific installed .sqpreset file without opening Premiere's New Sequence dialog. For footage-driven edits, prefer create_sequence_from_clips; for an empty copy of an existing sequence, use duplicate_sequence with clearContents=true. It is categorised as a Write tool in the Adobe Premiere Pro MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
create_sequence accepts 2 parameters: name, presetPath. Required: name, presetPath. The full parameter table on this page comes from the server's own tool schema.
Register the Adobe Premiere Pro 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 Adobe Premiere Pro. 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 Adobe Premiere Pro MCP server (adobe-premiere-pro-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Adobe Premiere Pro, and thousands of servers like it.
This server
Across the catalogue