replace_clip
Replaces a clip on the timeline with another media item.
This record as markdown: /tools/adobe-premiere-pro-mcp/replace-clip.md
What replace_clip does on Adobe Premiere Pro
AI agents use replace_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 replace |
preserveEffects | boolean | — | Whether to keep effects and settings (default: true) |
newProjectItemId | string | Yes | The ID of the new project item to use |
Parameters from the server's own tool schema.
Why replace_clip is rated Medium
The tool performs a non-destructive modification of timeline content. While it changes existing data (the clip being replaced), the operation is reversible through undo functionality typical in video editing software. This qualifies as Write rather than Destructive because the original clip can be recovered.
From the tool's definition Tool description: 'Replaces a clip on the timeline with another media item.' This modifies existing timeline content by substituting one clip for another, which is a reversible change to the project.
Attacks that exploit this kind of access
The rule that runs replace_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 replace_clip, this is the rule to start with:
replace_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 replace_clip call is checked against it from then on.
Questions about replace_clip
Replaces a clip on the timeline with another media item. 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.
replace_clip accepts 3 parameters: clipId, preserveEffects, newProjectItemId. Required: clipId, newProjectItemId. 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 replace_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.
replace_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 replace_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 replace_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.
replace_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