lock_track
Locks or unlocks a track to prevent/allow editing.
This record as markdown: /tools/adobe-premiere-pro-mcp/lock-track.md
What lock_track does on Adobe Premiere Pro
AI agents use lock_track 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 |
|---|---|---|---|
locked | boolean | Yes | Whether to lock (true) or unlock (false) |
trackType | string | Yes | Type of track |
sequenceId | string | Yes | The ID of the sequence |
trackIndex | number | Yes | The index of the track |
Parameters from the server's own tool schema.
Why lock_track is rated Medium
This tool changes the editable state of a track (locking/unlocking), which is a reversible write operation that modifies project metadata but does not create, delete, or execute external code. The action is fully undoable by calling the tool again with opposite parameters. While it affects editing permissions, it does not destructively delete content, execute arbitrary commands, or trigger financial transactions.
From the tool's definition Tool name 'lock_track' and description 'Locks or unlocks a track to prevent/allow editing' indicates reversible modification of track state/metadata in Adobe Premiere Pro.
Attacks that exploit this kind of access
The rule that runs lock_track 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 lock_track, this is the rule to start with:
lock_track 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 lock_track call is checked against it from then on.
Questions about lock_track
Locks or unlocks a track to prevent/allow editing. 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.
lock_track accepts 4 parameters: locked, trackType, sequenceId, trackIndex. Required: locked, trackType, sequenceId, trackIndex. 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 lock_track: 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.
lock_track 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 lock_track 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 lock_track. 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.
lock_track 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