update_marker
Updates an existing marker's properties.
This record as markdown: /tools/adobe-premiere-pro-mcp/update-marker.md
What update_marker does on Adobe Premiere Pro
AI agents use update_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 | — | New name for the marker |
color | string | — | New color |
comment | string | — | New comment |
markerId | string | Yes | The ID of the marker to update |
sequenceId | string | Yes | The ID of the sequence |
Parameters from the server's own tool schema.
Why update_marker is rated Medium
An AI agent can call update_marker faster than any human can review: one bad instruction and it creates or modifies resources in Adobe Premiere Pro by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs update_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 update_marker, this is the rule to start with:
update_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 update_marker call is checked against it from then on.
Questions about update_marker
Updates an existing marker's properties. 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.
update_marker accepts 5 parameters: name, color, comment, markerId, sequenceId. Required: markerId, 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 update_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.
update_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 update_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 update_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.
update_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