move_clip
Moves a clip to a different position on the timeline.
This record as markdown: /tools/adobe-premiere-pro-mcp/move-clip.md
What move_clip does on Adobe Premiere Pro
AI agents use move_clip 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 |
|---|---|---|---|
clipId | string | Yes | The ID of the clip to move |
newTime | number | Yes | The new time position in seconds |
newTrackIndex | number | — | The new track index (if moving to different track) |
Parameters from the server's own tool schema.
Why move_clip is rated Medium
Moving a clip is a reversible modification of project data. It does not delete content (Destructive), execute arbitrary code (Execute), involve financial transactions (Financial), or merely query information (Read). It falls squarely into Write because it changes the composition of the timeline in a way that can be undone.
From the tool's definition Tool description states it 'Moves a clip to a different position on the timeline' — this modifies the state of a video editing project by repositioning content.
Attacks that exploit this kind of access
The rule that runs move_clip 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 move_clip, this is the rule to start with:
move_clip 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 move_clip call is checked against it from then on.
Questions about move_clip
Moves a clip to a different position on the timeline. 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.
move_clip accepts 3 parameters: clipId, newTime, newTrackIndex. Required: clipId, newTime. 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 move_clip: 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.
move_clip 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 move_clip 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 move_clip. 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.
move_clip 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