Render the current timeline using a Quick Export preset. Mirrors Project.RenderWithQuickExport(preset_name, {param_dict}) per docs line 179. Args: preset_name: Name of the Quick Export preset (from get_quick_export_render_presets). target_dir: Output directory; maps to TargetDir in param_dict. cu...
AI agents invoke render_with_quick_export 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.
This tool triggers an external rendering operation in DaVinci Resolve, producing output files on disk. It executes a workflow (rendering/encoding) rather than simply reading or writing data reversibly. The blast radius is high because it can write large output files to arbitrary directories and potentially trigger uploads to external services (enable_upload parameter).
From the tool's definition Render the current timeline using a Quick Export preset
Documented attack patterns abuse exactly the kind of access render_with_quick_export 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 render_with_quick_export:
{
"version": "1",
"default": "deny",
"tools": {
"render_with_quick_export": {
"limits": [
{
"counter": "render_with_quick_export_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}render_with_quick_export 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.
Free to start. No card required.
Render the current timeline using a Quick Export preset. Mirrors Project.RenderWithQuickExport(preset_name, {param_dict}) per docs line 179. Args: preset_name: Name of the Quick Export preset (from get_quick_export_render_presets). target_dir: Output directory; maps to TargetDir in param_dict. custom_name: Output filename; maps to CustomName. video_quality: Video quality setting (int or string per render-settings spec); maps to VideoQuality. enable_upload: Enable direct upload for supported web presets; maps to EnableUpload. 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 render_with_quick_export: 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.
render_with_quick_export 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 render_with_quick_export 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 render_with_quick_export. 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.
render_with_quick_export 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.