conform_qc_package
Build a deliverable package (media mode × formats {otio,fcp7Xml,aaf,drp}) + V2 flag track + provenance manifest from a conformed timeline.
This record as markdown: /tools/samuelgursky-davinci-resolve-mcp/conform-qc-package.md
What conform_qc_package does on DaVinci Resolve MCP
AI agents invoke conform_qc_package to trigger actions in DaVinci Resolve MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why conform_qc_package is rated High
This tool orchestrates a complex multi-step operation: generating multiple export files in various formats (OTIO, FCP7 XML, AAF, DRP), adding a flag track, and creating a provenance manifest from a timeline. It triggers external operations with significant side effects (file creation, timeline modification) that go beyond simple writes.
From the tool's definition Build a deliverable package (media mode × formats {otio,fcp7Xml,aaf,drp}) + V2 flag track + provenance manifest from a conformed timeline
Attacks that exploit this kind of access
The rule that runs conform_qc_package 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 conform_qc_package, this is the rule to start with:
conform_qc_package stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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 conform_qc_package call is checked against it from then on.
Questions about conform_qc_package
Build a deliverable package (media mode × formats {otio,fcp7Xml,aaf,drp}) + V2 flag track + provenance manifest from a conformed timeline. It is categorised as a Execute tool in the DaVinci Resolve MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the DaVinci Resolve MCP server in PolicyLayer and add a rule for conform_qc_package: 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.
conform_qc_package is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the conform_qc_package 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 conform_qc_package. 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.
conform_qc_package 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.
Across the catalogue