Markers and playhead operations on the current timeline. Actions: add(frame|frame_id|frameId|timecode?, color?, name?, note?, duration?, custom_data?) -> {success, frame} If frame/timecode is omitted, add uses the current playhead timecode. get_all() -> {markers} get_by_custom_data(custom_data) -...
AI agents use timeline_markers 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 modifies timeline state through marker creation, updates, and deletion. Although delete operations exist, markers are non-destructive metadata overlays—they can be easily re-added or undone. The primary risk is unintended modification of a project's marker structure, which is a Write-category operation.
From the tool's definition The tool provides actions to add, update, and delete markers on a timeline: add(), update_custom_data(), delete_by_color(), and delete_at_frame().
Documented attack patterns abuse exactly the kind of access timeline_markers 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 timeline_markers:
{
"version": "1",
"default": "deny",
"tools": {
"timeline_markers": {
"limits": [
{
"counter": "timeline_markers_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}timeline_markers 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.
Markers and playhead operations on the current timeline. Actions: add(frame|frame_id|frameId|timecode?, color?, name?, note?, duration?, custom_data?) -> {success, frame} If frame/timecode is omitted, add uses the current playhead timecode. get_all() -> {markers} get_by_custom_data(custom_data) -> {markers} update_custom_data(frame|frame_id|frameId|timecode, custom_data) -> {success} get_custom_data(frame|frame_id|frameId|timecode) -> {data} delete_by_color(color) -> {success} delete_at_frame(frame|frame_id|frameId|timecode) -> {success} delete_by_custom_data(custom_data) -> {success} get_current_timecode() -> {timecode} set_current_timecode(timecode) -> {success} get_current_video_item() -> {name, id} get_thumbnail() -> {thumbnail} get_thumbnail_image() -> MCP image content for the current Color-page frame annotation_capabilities() -> {scopes, marker_colors, frame_aliases} probe_annotations(scope?, ...) -> {scopes, count} normalize_marker_payload(frame|timecode?, color?, name?, note?, duration?, custom_data?) -> {marker} copy_annotations(source={scope,...}, target={scope,...}, include_flags?, include_clip_color?) -> {success} move_annotations(source={scope,...}, target={scope,...}) -> {success} sync_marker_custom_data(scope?, frame|timecode, custom_data, ...) -> {success} clear_annotations_by_scope(scope?, color?, custom_data?, all?, clear_flags?, clear_clip_color?) -> {success} export_review_report(scope?, include_capabilities?) -> {title, annotations, capabilities?} annotation_boundary_report(scope?) -> {capabilities, annotations}. 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 timeline_markers: 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.
timeline_markers 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 timeline_markers 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 timeline_markers. 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.
timeline_markers 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.