AI agents use resolve_add_clip_mattes to create or update resources in Resolve — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Resolve environment.
This tool modifies project data by adding matte files to clips—a reversible write operation. It does not execute arbitrary commands, delete data, move money, or trigger external operations with unpredictable effects. The severity is medium because incorrect matte assignments could degrade project integrity or require manual correction, but the operation itself is non-destructive and localized to media pool metadata.
From the tool's definition Tool name 'resolve_add_clip_mattes' and description 'Add matte files to a media pool clip' indicate the tool creates or modifies clip metadata/associations within a DaVinci Resolve project.
Attacks that exploit this kind of access
Add matte files to a media pool clip. It is categorised as a Write tool in the Resolve MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Resolve MCP server in PolicyLayer and add a rule for resolve_add_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 Resolve. Nothing to install.
resolve_add_clip_mattes is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the resolve_add_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.
Set action: deny in the PolicyLayer policy for resolve_add_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.
resolve_add_clip_mattes is provided by the Resolve MCP server (jenkinsm13/resolve-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →