New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

delete_clip_marker_at_frame

Delete a marker at a specific frame on a clip.

SERVERDaVinci Resolve MCP SOURCEsamuelgursky/davinci-resolve-mcp
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/samuelgursky-davinci-resolve-mcp/delete-clip-marker-at-frame.md

What delete_clip_marker_at_frame does on DaVinci Resolve MCP

AI agents call delete_clip_marker_at_frame 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_at_frame is rated Critical

The tool permanently removes a marker from a clip, which cannot be undone programmatically through this API. While the impact is scoped to metadata (a marker) rather than media files, it is still a destructive action that destroys user-created annotations.

From the tool's definition Tool name contains 'delete' and description states 'Delete a marker at a specific frame on a clip' — this is an irreversible removal of data (a marker annotation).

Questions about delete_clip_marker_at_frame

What does the delete_clip_marker_at_frame tool do? +

Delete a marker at a specific frame on a clip. 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.

More on DaVinci Resolve, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of DaVinci Resolve's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.