Critical Risk →

clear_clip_flags

Clear flags on a clip. Args: clip_id: Unique ID of the clip. color: Specific color to clear, or empty for all colors.

How to control clear_clip_flags ↓

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

Critical Risk

Clearing flags is an irreversible removal of metadata annotations on a clip. There is no indication of an undo mechanism, and clearing 'all colors' could wipe all flag annotations simultaneously. This constitutes destructive modification of clip metadata rather than a simple write/update.

From the tool's definition "Clear flags on a clip" and parameter "color: Specific color to clear, or empty for all colors" — removes/deletes flag metadata from a clip, potentially all flags at once if no color is specified

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

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

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "clear_clip_flags"
  ]
}

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

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

Free to start. No card required.

Go deeper

What does the clear_clip_flags tool do? +

Clear flags on a clip. Args: clip_id: Unique ID of the clip. color: Specific color to clear, or empty for all colors. 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 clear_clip_flags? +

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

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

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

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

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

Free to start. No card required.

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

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.