timeline_delete_marker_by_custom_data

THE RISK

Critical Risk

This tool performs an irreversible deletion operation on timeline markers. Once deleted, the marker cannot be recovered without undo functionality external to the tool's scope. While the blast radius is somewhat contained (only markers are affected, not source media), the destructive nature and inability to undo through the tool itself justifies the 'Destructive' category.

From the tool's definition Tool name contains 'delete' and description states 'Delete a timeline marker by custom data.' The action irreversibly removes a marker from the timeline.

Documented attack patterns abuse exactly the kind of access timeline_delete_marker_by_custom_data gives an agent:

HOW TO CONTROL TIMELINE_DELETE_MARKER_BY_CUSTOM_DATA

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_delete_marker_by_custom_data:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "timeline_delete_marker_by_custom_data"
  ]
}

timeline_delete_marker_by_custom_data disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register DaVinci Resolve MCP — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

More DaVinci Resolve MCP tools

Destructive clear_clip_flags Clear flags on a clip. Args: clip_id: Unique ID of the clip. color: S Destructive clear_clip_transcription Clear transcription for a specific clip. Args: clip_id: Unique ID of the clip Destructive clear_folder_transcription Clear audio transcription for all clips in a folder. Args: folder_name: N Destructive clear_transcription Clear audio transcription for a clip. Args: clip_name: Name of the clip t Destructive dctl Author and install DCTL files (Color page custom shaders + ACES transforms). Regular Destructive delete_clip_marker_at_frame Delete a marker at a specific frame on a clip. Args: clip_id: Unique ID of th Destructive delete_clip_marker_by_custom_data Delete a marker by its custom data string. Args: clip_id: Unique ID of the cl Destructive delete_clip_markers_by_color Delete all markers of a specific color on a clip. Args: clip_id: Unique ID of

All 369 DaVinci Resolve MCP tools →

Destructive tools on other servers

Frida Game Hacking MCP clear_scan MegaMemory remove_concept Frida Agent MCP kill_app 1MCP Server mcp_uninstall

Go deeper

Critical-risk tools in DaVinci Resolve MCP → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

What does the timeline_delete_marker_by_custom_data tool do? +

Delete a timeline marker by custom data. Args: custom_data: Custom data of the marker to delete. 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.

How do I enforce a policy on timeline_delete_marker_by_custom_data? +

Register the DaVinci Resolve MCP server in PolicyLayer and add a rule for timeline_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.

What risk level is timeline_delete_marker_by_custom_data? +

timeline_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.

Can I rate-limit timeline_delete_marker_by_custom_data? +

Yes. Add a rate_limit block to the timeline_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.

How do I block timeline_delete_marker_by_custom_data completely? +

Set action: deny in the PolicyLayer policy for timeline_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.

What MCP server provides timeline_delete_marker_by_custom_data? +

timeline_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.

Enforce policy on every DaVinci Resolve MCP tool call.

Deterministic rules across all 369 DaVinci Resolve MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

GOVERN DAVINCI RESOLVE →

Free to start. No card required.

369 DaVinci Resolve MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

timeline_delete_marker_by_custom_data

// WHAT TIMELINE_DELETE_MARKER_BY_CUSTOM_DATA ON DAVINCI RESOLVE MCP DOES

// THE RISK

// HOW TO CONTROL TIMELINE_DELETE_MARKER_BY_CUSTOM_DATA

// EXPLORE