timeline_create_compound_clip
A write tool on the DaVinci Resolve MCP server.
This record as markdown: /tools/samuelgursky-davinci-resolve-mcp/timeline-create-compound-clip.md
What timeline_create_compound_clip does on DaVinci Resolve MCP
AI agents use timeline_create_compound_clip 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.
Why timeline_create_compound_clip is rated Medium
This tool creates a new compound clip, which is a reversible modification to the DaVinci Resolve project. The action is creative/additive rather than destructive (can be undone), executable (no code execution or external triggers), or financial. While the description is empty, the naming pattern and context of sibling tools confirm this is a Write operation.
From the tool's definition Tool name 'timeline_create_compound_clip' indicates creation of a new compound clip in the timeline. Sibling tools include 'add_clip_marker', 'add_keyframe', 'add_render_job', and 'add_items_to_media_pool_from_storage', all of which are Write operations that…
Attacks that exploit this kind of access
The rule that runs timeline_create_compound_clip safely
PolicyLayer is an MCP gateway: it sits between your AI agents and DaVinci Resolve MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For timeline_create_compound_clip, this is the rule to start with:
timeline_create_compound_clip 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.
The button opens the PolicyLayer dashboard: create your workspace, connect DaVinci Resolve MCP, apply this rule, and every timeline_create_compound_clip call is checked against it from then on.
Questions about timeline_create_compound_clip
timeline_create_compound_clip is a write tool on the DaVinci Resolve MCP server. 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 timeline_create_compound_clip: 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.
timeline_create_compound_clip 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 timeline_create_compound_clip 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 timeline_create_compound_clip. 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.
timeline_create_compound_clip 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.
More on DaVinci Resolve, and thousands of servers like it.
This server
Across the catalogue