add_render_job
Add a render job based on current render settings to the render queue.
This record as markdown: /tools/samuelgursky-davinci-resolve-mcp/add-render-job.md
What add_render_job does on DaVinci Resolve MCP
AI agents invoke add_render_job 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 add_render_job is rated High
Adding a render job triggers an external operation in DaVinci Resolve — it queues a potentially long-running rendering process that consumes system resources and produces output files. This is an execution of an external workflow rather than a simple data write, and misuse could queue unintended renders consuming significant CPU/GPU resources.
From the tool's definition Add a render job based on current render settings to the render queue
Attacks that exploit this kind of access
The rule that runs add_render_job 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 add_render_job, this is the rule to start with:
add_render_job 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 add_render_job call is checked against it from then on.
Questions about add_render_job
Add a render job based on current render settings to the render queue. 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 add_render_job: 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_render_job 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 add_render_job 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_render_job. 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_render_job 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