Create a stacked multicam prep timeline from Media Pool clips. This does not create a native Resolve multicam clip because the public scripting API does not expose native multicam creation. It creates a prep timeline with one angle per video track and optional matching audio tracks. Args: name: N...
AI agents use setup_multicam_timeline 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 new timeline data structures in the video editing project, which is a reversible modification operation. It does not delete data (making it not Destructive), does not execute arbitrary code or external processes (making it not Execute), and does not involve financial transactions (making it not Financial). While it modifies project state, the changes can be undone through normal editing operations.
From the tool's definition The tool description states it will 'Create a stacked multicam prep timeline' and 'creates a prep timeline with one angle per video track.' This is a creation operation that modifies the DaVinci Resolve project by adding new timeline structures.
Documented attack patterns abuse exactly the kind of access setup_multicam_timeline 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 setup_multicam_timeline:
{
"version": "1",
"default": "deny",
"tools": {
"setup_multicam_timeline": {
"limits": [
{
"counter": "setup_multicam_timeline_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}setup_multicam_timeline 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.
Create a stacked multicam prep timeline from Media Pool clips. This does not create a native Resolve multicam clip because the public scripting API does not expose native multicam creation. It creates a prep timeline with one angle per video track and optional matching audio tracks. Args: name: Name for the setup timeline. clip_ids: Simple list of MediaPoolItem unique IDs, one per angle. angles: Detailed angle rows with clip_id, optional angle_name, start_frame/end_frame, record_frame, source_timecode, track_index. sync_mode: 'stack_start', 'record_frame', or 'source_timecode'. include_audio: Also append audio-only rows. audio_track_mode: 'matching' for per-angle audio tracks, or 'first'. start_timecode: Optional timeline start timecode to set after creation. timeline_start_timecode: Base timecode for source_timecode sync math. record_frame_start: Timeline-relative start frame for stack_start mode. frame_rate: Fallback frame rate for duration/timecode parsing. audio_type: Resolve audio track type when tracks must be added. dry_run: Return the plan without creating a timeline. 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 setup_multicam_timeline: 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.
setup_multicam_timeline 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 setup_multicam_timeline 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 setup_multicam_timeline. 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.
setup_multicam_timeline 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.