ti_delete_marker_by_custom_data
Delete a marker by custom data on a timeline item.
This record as markdown: /tools/samuelgursky-davinci-resolve-mcp/ti-delete-marker-by-custom-data.md
What ti_delete_marker_by_custom_data does on DaVinci Resolve MCP
AI agents call ti_delete_marker_by_custom_data to permanently remove resources in DaVinci Resolve MCP, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why ti_delete_marker_by_custom_data is rated Critical
This tool performs an irreversible deletion operation on timeline metadata (markers). While markers are not the primary video content, they represent important editorial metadata that documents decisions, cues, or annotations made during editing. Deletion cannot be reversed by the tool, and an AI agent could maliciously or accidentally remove markers that are critical to the project workflow.
From the tool's definition Tool name contains 'delete' and description states 'Delete a marker by custom data on a timeline item.' The action is irreversible—deleting a marker from a video timeline cannot be undone programmatically by the tool itself.
Attacks that exploit this kind of access
The rule that runs ti_delete_marker_by_custom_data safely
PolicyLayer is an MCP gateway: it sits between your AI agents and DaVinci Resolve MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For ti_delete_marker_by_custom_data, this is the rule to start with:
ti_delete_marker_by_custom_data is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect DaVinci Resolve MCP, apply this rule, and every ti_delete_marker_by_custom_data call is checked against it from then on.
Questions about ti_delete_marker_by_custom_data
Delete a marker by custom data on a timeline item. It is categorised as a Destructive tool in the DaVinci Resolve MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the DaVinci Resolve MCP server in PolicyLayer and add a rule for ti_delete_marker_by_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_delete_marker_by_custom_data is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the ti_delete_marker_by_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_delete_marker_by_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_delete_marker_by_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.
More on DaVinci Resolve, and thousands of servers like it.
Across the catalogue