duplicate_sequence
Creates a copy of an existing sequence with a new name. Set clearContents=true to get an EMPTY copy that inherits the source sequence's exact settings (frame rate, resolution, track layout) — the reliable way to auto-create a correctly-specced blank target, since create_sequence ignores frame rate.
This record as markdown: /tools/adobe-premiere-pro-mcp/duplicate-sequence.md
What duplicate_sequence does on Adobe Premiere Pro
AI agents use duplicate_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 |
|---|---|---|---|
newName | string | Yes | The name for the new sequence copy |
sequenceId | string | Yes | The ID of the sequence to duplicate |
clearContents | boolean | — | When true, remove all clips from the copy so it is empty but keeps the source's frame rate/resolution/track layout. Default false (full copy). |
Parameters from the server's own tool schema.
Why duplicate_sequence is rated Medium
An AI agent can call duplicate_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 duplicate_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 duplicate_sequence, this is the rule to start with:
duplicate_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 duplicate_sequence call is checked against it from then on.
Questions about duplicate_sequence
Creates a copy of an existing sequence with a new name. Set clearContents=true to get an EMPTY copy that inherits the source sequence's exact settings (frame rate, resolution, track layout) — the reliable way to auto-create a correctly-specced blank target, since create_sequence ignores frame rate. 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.
duplicate_sequence accepts 3 parameters: newName, sequenceId, clearContents. Required: newName, sequenceId. 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 duplicate_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.
duplicate_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 duplicate_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 duplicate_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.
duplicate_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