create_subsequence
Creates a subsequence from the in/out points of a sequence.
This record as markdown: /tools/adobe-premiere-pro-mcp/create-subsequence.md
What create_subsequence does on Adobe Premiere Pro
AI agents use create_subsequence 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 |
|---|---|---|---|
sequenceId | string | Yes | The ID of the source sequence |
ignoreTrackTargeting | boolean | — | Whether to ignore track targeting (default: false) |
Parameters from the server's own tool schema.
Why create_subsequence is rated Medium
This tool creates a new media object (subsequence) from existing timeline segments, which is a reversible write operation. While it modifies the project state by adding a new element, it does not execute arbitrary code, delete data irreversibly, or move money. The 'medium' severity reflects that an AI misuse could generate unwanted subsequences, requiring cleanup but no permanent loss.
From the tool's definition Tool description states it 'Creates a subsequence from the in/out points of a sequence' — the word 'Creates' indicates a write operation that generates new data (a subsequence) within Adobe Premiere Pro.
Attacks that exploit this kind of access
The rule that runs create_subsequence 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_subsequence, this is the rule to start with:
create_subsequence 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_subsequence call is checked against it from then on.
Questions about create_subsequence
Creates a subsequence from the in/out points of a sequence. 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_subsequence accepts 2 parameters: sequenceId, ignoreTrackTargeting. Required: 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 create_subsequence: 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_subsequence 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_subsequence 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_subsequence. 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_subsequence 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