delete_clip_marker_at_frame

THE RISK

Critical Risk

This tool performs an irreversible deletion operation on project data. While the blast radius is bounded to marker metadata rather than entire clips or media, the action cannot be undone programmatically and could disrupt video editing workflows if markers are deleted incorrectly. Destructive operations carry higher severity than Write operations due to their permanent nature.

From the tool's definition Tool name contains 'delete' and description states 'Delete a marker at a specific frame on a clip.' The action irreversibly removes metadata (markers) from video editing projects.

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

HOW TO CONTROL DELETE_CLIP_MARKER_AT_FRAME

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

policy.json

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

delete_clip_marker_at_frame 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_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 Destructive delete_clip_mattes Delete clip mattes from a MediaPoolItem. Args: clip_id: Unique ID of the clip

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 delete_clip_marker_at_frame tool do? +

Delete a marker at a specific frame on a clip. Args: clip_id: Unique ID of the clip. frame_id: Frame number 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 delete_clip_marker_at_frame? +

Register the DaVinci Resolve MCP server in PolicyLayer and add a rule for delete_clip_marker_at_frame: 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 delete_clip_marker_at_frame? +

delete_clip_marker_at_frame 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 delete_clip_marker_at_frame? +

Yes. Add a rate_limit block to the delete_clip_marker_at_frame 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 delete_clip_marker_at_frame completely? +

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

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

// WHAT DELETE_CLIP_MARKER_AT_FRAME ON DAVINCI RESOLVE MCP DOES

// THE RISK

// HOW TO CONTROL DELETE_CLIP_MARKER_AT_FRAME

// EXPLORE