batch_add_transitions
Adds a transition to all clip boundaries on a track. Useful for quickly adding cross dissolves or other transitions between every clip.
This record as markdown: /tools/adobe-premiere-pro-mcp/batch-add-transitions.md
What batch_add_transitions does on Adobe Premiere Pro
AI agents use batch_add_transitions 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 |
|---|---|---|---|
duration | number | Yes | The duration of each transition in seconds |
sequenceId | string | Yes | The ID of the sequence |
trackIndex | number | Yes | The video track index (0-based) |
transitionName | string | Yes | The name of the transition (e.g., "Cross Dissolve") |
Parameters from the server's own tool schema.
Why batch_add_transitions is rated Medium
The tool performs batch modification of timeline data by adding transition elements to multiple clip boundaries. This is a Write operation because it creates and applies new effects/objects to the project (reversible via undo in the UI, but each API call is a state-modifying write).
From the tool's definition Tool description: 'Adds a transition to all clip boundaries on a track.' This creates new transition objects in the Premiere Pro timeline, modifying the project's composition irreversibly by inserting visual effects at clip boundaries.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs batch_add_transitions 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 batch_add_transitions, this is the rule to start with:
batch_add_transitions 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 batch_add_transitions call is checked against it from then on.
Questions about batch_add_transitions
Adds a transition to all clip boundaries on a track. Useful for quickly adding cross dissolves or other transitions between every clip. 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.
batch_add_transitions accepts 4 parameters: duration, sequenceId, trackIndex, transitionName. Required: duration, sequenceId, trackIndex, transitionName. 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 batch_add_transitions: 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.
batch_add_transitions 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 batch_add_transitions 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 batch_add_transitions. 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.
batch_add_transitions 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