razor_timeline_at_time
Cuts across multiple tracks in a sequence at an absolute timeline time. If no track arrays are provided, all video and audio tracks are cut.
This record as markdown: /tools/adobe-premiere-pro-mcp/razor-timeline-at-time.md
What razor_timeline_at_time does on Adobe Premiere Pro
AI agents use razor_timeline_at_time 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 |
|---|---|---|---|
time | number | Yes | Absolute timeline time in seconds where the cut should occur. |
sequenceId | string | — | Optional sequence ID. Defaults to the active sequence. |
audioTrackIndices | array | — | Optional audio track indices to cut. Defaults to all audio tracks. |
videoTrackIndices | array | — | Optional video track indices to cut. Defaults to all video tracks. |
Parameters from the server's own tool schema.
Why razor_timeline_at_time is rated Medium
This tool modifies video project state by splitting tracks at specified times, but does not delete content or remove data irreversibly—the cut can be undone. It's a Write operation (modifying/creating new track segments) rather than Destructive (which would require permanent data loss).
From the tool's definition Tool description states it 'Cuts across multiple tracks in a sequence at an absolute timeline time,' which modifies the timeline structure by inserting cut points. The operation is reversible through undo functionality standard in Premiere Pro.
Attacks that exploit this kind of access
The rule that runs razor_timeline_at_time 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 razor_timeline_at_time, this is the rule to start with:
razor_timeline_at_time 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 razor_timeline_at_time call is checked against it from then on.
Questions about razor_timeline_at_time
Cuts across multiple tracks in a sequence at an absolute timeline time. If no track arrays are provided, all video and audio tracks are cut. 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.
razor_timeline_at_time accepts 4 parameters: time, sequenceId, audioTrackIndices, videoTrackIndices. Required: time. 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 razor_timeline_at_time: 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.
razor_timeline_at_time 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 razor_timeline_at_time 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 razor_timeline_at_time. 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.
razor_timeline_at_time 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