Critical Risk →

delete_clip_mattes

Delete clip mattes from a MediaPoolItem. Args: clip_id: Unique ID of the clip. matte_paths: List of matte file paths to delete.

How to control delete_clip_mattes ↓

AI agents call delete_clip_mattes 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

This tool permanently removes matte files associated with video clips in the DaVinci Resolve media pool. Mattes are important compositing assets, and their deletion cannot be undone through the tool itself. An AI agent misusing this could irreversibly destroy editing work by removing critical visual elements needed for projects.

From the tool's definition Tool name is 'delete_clip_mattes' and description states 'Delete clip mattes from a MediaPoolItem.' The verb 'Delete' combined with the action of removing matte files indicates irreversible data removal.

Documented attack patterns abuse exactly the kind of access delete_clip_mattes 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 delete_clip_mattes:

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

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

Delete clip mattes from a MediaPoolItem. Args: clip_id: Unique ID of the clip. matte_paths: List of matte file paths 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_mattes? +

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

delete_clip_mattes 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_mattes? +

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

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

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