# ti_add_marker A write tool on the DaVinci Resolve MCP MCP server. Agent View of the PolicyLayer registry record for `ti_add_marker`. HTML page: https://policylayer.com/tools/samuelgursky-davinci-resolve-mcp/ti-add-marker ## Facts - Tool: `ti_add_marker` - 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: Write (Medium risk) - Registry record: grade F, identity unverified - Server rate-limited: no - Parameters: 0 - Recommended policy verdict: Rate-limited ## Example call (MCP tools/call, JSON-RPC 2.0) ```json { "jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": { "name": "ti_add_marker", "arguments": {} } } ``` ## Why ti_add_marker is rated Medium Adding markers to a video timeline is a Write operation: it creates editable metadata without irreversibly destroying data. The 'add_' prefix and sibling tools on a video editing server confirm this classification. Severity is medium because malicious marker addition could corrupt project organization or workflow, but changes are reversible. Confidence is reduced from higher due to the empty tool description. From the tool's own definition: "Tool name 'ti_add_marker' indicates marker creation (add_*), and sibling tools like 'add_clip_marker' and 'add_keyframe' confirm this server performs content modification." ## Use case AI agents use ti_add_marker to create or update resources in DaVinci Resolve MCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your DaVinci Resolve MCP environment. ## Recommended policy (PolicyLayer) Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches DaVinci Resolve MCP: ```json { "version": "1", "default": "deny", "tools": { "ti_add_marker": { "limits": [ { "counter": "ti_add_marker_rate", "window": "minute", "max": 30, "scope": "grant" } ] } } } ``` ## 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_markers_by_color` — Destructive — https://policylayer.com/tools/samuelgursky-davinci-resolve-mcp/delete-clip-markers-by-color.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 - …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