Update marker custom data. Args: frame_id: Frame number. custom_data: New custom data. item_index: 0-based item index. Default: 0.
AI agents use ti_update_marker_custom_data 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 data reversibly—updating marker metadata can be undone or corrected within DaVinci Resolve. It does not execute arbitrary code, delete data irreversibly, or move financial resources. The blast radius is limited to marker metadata in the current project, making it a Write classification with medium severity since unintended modifications to markers could disrupt an editing workflow.
From the tool's definition Tool name 'update_marker_custom_data' and description 'Update marker custom data' indicate modification of existing data. The parameters (frame_id, custom_data, item_index) show the tool modifies metadata associated with video markers in a timeline.
Documented attack patterns abuse exactly the kind of access ti_update_marker_custom_data 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_update_marker_custom_data:
{
"version": "1",
"default": "deny",
"tools": {
"ti_update_marker_custom_data": {
"limits": [
{
"counter": "ti_update_marker_custom_data_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}ti_update_marker_custom_data 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.
Update marker custom data. Args: frame_id: Frame number. custom_data: New custom data. item_index: 0-based item index. Default: 0. 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_update_marker_custom_data: 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_update_marker_custom_data 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_update_marker_custom_data 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_update_marker_custom_data. 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_update_marker_custom_data 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.