Add a marker to a timeline item. Args: frame_id: Frame offset within the item. color: Marker color. name: Marker name. note: Marker note. Default: ''. duration: Duration in frames. Default: 1. custom_data: Custom data. Default: ''. item_index: 0-based item index. Default: 0. track_type: 'video' o...
AI agents use ti_add_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.
Adding markers to timeline items is a reversible modification operation that creates metadata annotations within the video editing project. Markers can be removed or edited, making this a Write action rather than destructive. The severity is low because markers are non-essential metadata that do not affect the underlying media or project structure; their misuse by an AI agent would have minimal blast radius.
From the tool's definition The tool 'ti_add_marker' adds a marker to a timeline item with parameters for frame_id, color, name, note, duration, custom_data, and track information. The description explicitly states it 'Add[s] a marker' which is a create/modify operation.
Documented attack patterns abuse exactly the kind of access ti_add_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 ti_add_marker:
{
"version": "1",
"default": "deny",
"tools": {
"ti_add_marker": {
"limits": [
{
"counter": "ti_add_marker_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}ti_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.
Free to start. No card required.
Add a marker to a timeline item. Args: frame_id: Frame offset within the item. color: Marker color. name: Marker name. note: Marker note. Default: ''. duration: Duration in frames. Default: 1. custom_data: Custom data. Default: ''. item_index: 0-based item index. Default: 0. track_type: 'video' or 'audio'. Default: 'video'. track_index: 1-based track index. Default: 1. 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 ti_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 DaVinci Resolve MCP. Nothing to install.
ti_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 ti_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 ti_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.
ti_add_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.