Add a marker to a Media Pool clip. Args: clip_id: Unique ID of the clip. frame_id: Frame number for the marker. color: Marker color (Blue, Cyan, Green, Yellow, Red, Pink, Purple, Fuchsia, Rose, Lavender, Sky, Mint, Lemon, Sand, Cocoa, Cream). name: Marker name. note: Marker note. Default: empty. ...
AI agents use add_clip_marker to create or update resources in DaVinci Resolve MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your DaVinci Resolve MCP environment.
This tool creates or modifies metadata (markers) on video clips in the media pool. It is reversible—markers can be removed or edited without data loss. It does not delete, execute code, or affect financial/destructive operations. This is a straightforward Write operation with minimal blast radius if misused by an AI agent (worst case: unwanted markers added to clips, easily removable).
From the tool's definition Tool description states 'Add a marker to a Media Pool clip' with parameters for clip_id, frame_id, color, name, note, duration, and custom_data. The verb 'Add' and the action of creating marker metadata on a clip indicate data creation/modification.
Documented attack patterns abuse exactly the kind of access add_clip_marker gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and DaVinci Resolve MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for add_clip_marker:
{
"version": "1",
"default": "deny",
"tools": {
"add_clip_marker": {
"limits": [
{
"counter": "add_clip_marker_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}add_clip_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.
Free to start. No card required.
Add a marker to a Media Pool clip. Args: clip_id: Unique ID of the clip. frame_id: Frame number for the marker. color: Marker color (Blue, Cyan, Green, Yellow, Red, Pink, Purple, Fuchsia, Rose, Lavender, Sky, Mint, Lemon, Sand, Cocoa, Cream). name: Marker name. note: Marker note. Default: empty. duration: Marker duration in frames. Default: 1. custom_data: Custom data string. Default: empty. It is categorised as a Write tool in the DaVinci Resolve MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the DaVinci Resolve MCP server in PolicyLayer and add a rule for add_clip_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 DaVinci Resolve MCP. Nothing to install.
add_clip_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_clip_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_clip_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_clip_marker is provided by the DaVinci Resolve MCP server (samuelgursky/davinci-resolve-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 369 DaVinci Resolve MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
369 DaVinci Resolve MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.