# delete_clip_markers_by_color

Delete all markers of a specific color on a clip.

Agent View of the PolicyLayer registry record for `delete_clip_markers_by_color`. HTML page: https://policylayer.com/tools/samuelgursky-davinci-resolve-mcp/delete-clip-markers-by-color

## Facts

- Tool: `delete_clip_markers_by_color`
- Server: DaVinci Resolve MCP (`samuelgursky/davinci-resolve-mcp`) — https://policylayer.com/tools/samuelgursky-davinci-resolve-mcp.md
- Homepage: https://github.com/samuelgursky/davinci-resolve-mcp
- Risk category: Destructive (Critical risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Hidden

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "delete_clip_markers_by_color",
    "arguments": {}
  }
}
```

## Why delete_clip_markers_by_color is rated Critical

This tool permanently removes markers from a clip without the ability to recover them (absent project backup/undo). While markers are metadata rather than the core media, their deletion is irreversible and could result in loss of important editing notes or cue points. This qualifies as Destructive rather than Write (which is reversible).

From the tool's own definition: "Tool name contains 'delete' and description states 'Delete all markers of a specific color on a clip' - this is an irreversible deletion operation that removes data from the video editing project."

## Use case

AI agents call delete_clip_markers_by_color 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.

## Recommended policy (PolicyLayer)

Verdict: **Hidden**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches DaVinci Resolve MCP:

```json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_clip_markers_by_color"
  ]
}
```

## Other tools on DaVinci Resolve MCP (354)

- `archive_project` — Destructive — https://policylayer.com/tools/samuelgursky-davinci-resolve-mcp/archive-project.md
- `clear_clip_flags` — Destructive — https://policylayer.com/tools/samuelgursky-davinci-resolve-mcp/clear-clip-flags.md
- `clear_clip_transcription` — Destructive — https://policylayer.com/tools/samuelgursky-davinci-resolve-mcp/clear-clip-transcription.md
- `clear_folder_transcription` — Destructive — https://policylayer.com/tools/samuelgursky-davinci-resolve-mcp/clear-folder-transcription.md
- `clear_transcription` — Destructive — https://policylayer.com/tools/samuelgursky-davinci-resolve-mcp/clear-transcription.md
- `close_project` — Destructive — https://policylayer.com/tools/samuelgursky-davinci-resolve-mcp/close-project.md
- `delete_burn_in_preset` — Destructive — https://policylayer.com/tools/samuelgursky-davinci-resolve-mcp/delete-burn-in-preset.md
- `delete_clip_marker_at_frame` — Destructive — https://policylayer.com/tools/samuelgursky-davinci-resolve-mcp/delete-clip-marker-at-frame.md
- `delete_clip_marker_by_custom_data` — Destructive — https://policylayer.com/tools/samuelgursky-davinci-resolve-mcp/delete-clip-marker-by-custom-data.md
- `delete_clip_mattes` — Destructive — https://policylayer.com/tools/samuelgursky-davinci-resolve-mcp/delete-clip-mattes.md
- `delete_color_group` — Destructive — https://policylayer.com/tools/samuelgursky-davinci-resolve-mcp/delete-color-group.md
- `delete_keyframe` — Destructive — https://policylayer.com/tools/samuelgursky-davinci-resolve-mcp/delete-keyframe.md
- `delete_layout_preset_tool` — Destructive — https://policylayer.com/tools/samuelgursky-davinci-resolve-mcp/delete-layout-preset-tool.md
- `delete_media_pool_clips` — Destructive — https://policylayer.com/tools/samuelgursky-davinci-resolve-mcp/delete-media-pool-clips.md
- `delete_media_pool_folders` — Destructive — https://policylayer.com/tools/samuelgursky-davinci-resolve-mcp/delete-media-pool-folders.md
- `delete_project` — Destructive — https://policylayer.com/tools/samuelgursky-davinci-resolve-mcp/delete-project.md
- `delete_project_folder` — Destructive — https://policylayer.com/tools/samuelgursky-davinci-resolve-mcp/delete-project-folder.md
- `delete_render_job` — Destructive — https://policylayer.com/tools/samuelgursky-davinci-resolve-mcp/delete-render-job.md
- `delete_render_preset` — Destructive — https://policylayer.com/tools/samuelgursky-davinci-resolve-mcp/delete-render-preset.md
- `delete_stills_from_album` — Destructive — https://policylayer.com/tools/samuelgursky-davinci-resolve-mcp/delete-stills-from-album.md
- `delete_timelines_by_id` — Destructive — https://policylayer.com/tools/samuelgursky-davinci-resolve-mcp/delete-timelines-by-id.md
- `delete_user_preferences_preset` — Destructive — https://policylayer.com/tools/samuelgursky-davinci-resolve-mcp/delete-user-preferences-preset.md
- `folder_clear_transcription` — Destructive — https://policylayer.com/tools/samuelgursky-davinci-resolve-mcp/folder-clear-transcription.md
- `folder_remove_motion_blur` — Destructive — https://policylayer.com/tools/samuelgursky-davinci-resolve-mcp/folder-remove-motion-blur.md
- `graph_reset_all_grades` — Destructive — https://policylayer.com/tools/samuelgursky-davinci-resolve-mcp/graph-reset-all-grades.md
- `quit_resolve` — Destructive — https://policylayer.com/tools/samuelgursky-davinci-resolve-mcp/quit-resolve.md
- `ti_clear_flags` — Destructive — https://policylayer.com/tools/samuelgursky-davinci-resolve-mcp/ti-clear-flags.md
- `ti_delete_fusion_comp` — Destructive — https://policylayer.com/tools/samuelgursky-davinci-resolve-mcp/ti-delete-fusion-comp.md
- `ti_delete_marker_at_frame` — Destructive — https://policylayer.com/tools/samuelgursky-davinci-resolve-mcp/ti-delete-marker-at-frame.md
- `ti_delete_marker_by_custom_data` — Destructive — https://policylayer.com/tools/samuelgursky-davinci-resolve-mcp/ti-delete-marker-by-custom-data.md
- …and 324 more: https://policylayer.com/tools/samuelgursky-davinci-resolve-mcp.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=samuelgursky-davinci-resolve-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/samuelgursky-davinci-resolve-mcp
