add_marker
Adds a marker to the timeline for navigation or notes.
This record as markdown: /tools/adobe-premiere-pro-mcp/add-marker.md
What add_marker does on Adobe Premiere Pro
AI agents use add_marker 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 |
|---|---|---|---|
name | string | Yes | The name/label for the marker |
time | number | Yes | The time in seconds where the marker should be placed |
color | string | — | Marker color (e.g., "red", "green", "blue") |
comment | string | — | Optional comment or description for the marker |
duration | number | — | Duration in seconds for a span marker (0 for point marker) |
sequenceId | string | Yes | The ID of the sequence to add the marker to |
Parameters from the server's own tool schema.
Why add_marker is rated Medium
Adding markers is a reversible write operation that modifies the project state by inserting navigational or notational elements. It does not execute arbitrary code, delete data, or trigger financial transactions. While it modifies the timeline structure, markers are non-destructive metadata that can be removed or edited.
From the tool's definition Tool name 'add_marker' combined with description 'Adds a marker to the timeline for notes' indicates creation of metadata/annotations within Adobe Premiere Pro. This is a modification operation that creates new data (markers) within the project timeline.
Attacks that exploit this kind of access
The rule that runs add_marker 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 add_marker, this is the rule to start with:
add_marker 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 add_marker call is checked against it from then on.
Questions about add_marker
Adds a marker to the timeline for navigation or notes. 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.
add_marker accepts 6 parameters: name, time, color, comment, duration, sequenceId. Required: name, time, sequenceId. 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 add_marker: 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.
add_marker 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 add_marker 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 add_marker. 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.
add_marker 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