delete_clip_marker_by_custom_data
Delete a marker by its custom data string.
This record as markdown: /tools/samuelgursky-davinci-resolve-mcp/delete-clip-marker-by-custom-data.md
What delete_clip_marker_by_custom_data does on DaVinci Resolve MCP
AI agents call delete_clip_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 delete_clip_marker_by_custom_data is rated Critical
This tool irreversibly removes data (a clip marker) from a DaVinci Resolve project. Markers in video editing projects are metadata used to annotate timelines and clips; deleting them cannot be undone programmatically through this tool.
From the tool's definition Tool name contains 'delete' and description states it will 'Delete a marker by its custom data string.' The action is irreversible—once deleted, the marker and its associated metadata cannot be recovered without undo functionality.
Attacks that exploit this kind of access
The rule that runs delete_clip_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 delete_clip_marker_by_custom_data, this is the rule to start with:
delete_clip_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 delete_clip_marker_by_custom_data call is checked against it from then on.
Questions about delete_clip_marker_by_custom_data
Delete a marker by its custom data string. 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 delete_clip_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.
delete_clip_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 delete_clip_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 delete_clip_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.
delete_clip_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