split_clip
Splits a clip at a specific time point, creating two separate clips.
This record as markdown: /tools/adobe-premiere-pro-mcp/split-clip.md
What split_clip does on Adobe Premiere Pro
AI agents use split_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 split |
splitTime | number | Yes | The time in seconds where to split the clip |
Parameters from the server's own tool schema.
Why split_clip is rated Medium
The split_clip action modifies the project by creating new clip objects, which is a write operation. It is reversible (clips can be rejoined or the action undone), so it does not qualify as Destructive. While it operates on a video editing timeline, it is not executing arbitrary code or shell commands (Execute category).
From the tool's definition Tool description states 'Splits a clip at a specific time point, creating two separate clips.' This creates new objects (two clips) from one existing clip, which is a reversible modification of the video project structure.
Attacks that exploit this kind of access
The rule that runs split_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 split_clip, this is the rule to start with:
split_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 split_clip call is checked against it from then on.
Questions about split_clip
Splits a clip at a specific time point, creating two separate clips. 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.
split_clip accepts 2 parameters: clipId, splitTime. Required: clipId, splitTime. 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 split_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.
split_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 split_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 split_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.
split_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