Add timeline mattes from Media Storage to a timeline item. Args: timeline_item_index: 0-based index of the item in the track. matte_paths: List of absolute file paths for the matte files. track_type: Track type ('video' or 'audio'). Default: 'video'. track_index: 1-based track index. Default: 1.
AI agents use add_timeline_mattes_to_media_pool 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.
This tool creates or modifies editing data within DaVinci Resolve by adding matte assets to a timeline, which is a reversible operation (mattes can be removed or replaced). It does not execute arbitrary code, delete data irreversibly, or move money. The moderate severity reflects that misuse could corrupt a video project's timeline, but changes are generally undoable within the editing workflow.
From the tool's definition add_timeline_mattes_to_media_pool adds mattes to a timeline item by accepting file paths and track parameters, modifying the timeline composition and media pool state.
Documented attack patterns abuse exactly the kind of access add_timeline_mattes_to_media_pool 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 add_timeline_mattes_to_media_pool:
{
"version": "1",
"default": "deny",
"tools": {
"add_timeline_mattes_to_media_pool": {
"limits": [
{
"counter": "add_timeline_mattes_to_media_pool_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}add_timeline_mattes_to_media_pool stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Add timeline mattes from Media Storage to a timeline item. Args: timeline_item_index: 0-based index of the item in the track. matte_paths: List of absolute file paths for the matte files. track_type: Track type ('video' or 'audio'). Default: 'video'. track_index: 1-based track index. Default: 1. It is categorised as a Write tool in the DaVinci Resolve MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the DaVinci Resolve MCP server in PolicyLayer and add a rule for add_timeline_mattes_to_media_pool: 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.
add_timeline_mattes_to_media_pool 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 add_timeline_mattes_to_media_pool 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 add_timeline_mattes_to_media_pool. 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.
add_timeline_mattes_to_media_pool 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.
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.