Start rendering the current project with optional preset and path.
AI agents invoke start_project_render to trigger actions in DaVinci Resolve MCP Server. 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 initiates a render operation, which executes a complex external process whose completion time, resource consumption, and output depend on project parameters. While not destructive (rendering doesn't delete data) or financial, it is Execute-class because it triggers a potentially long-running, resource-intensive operation that the AI agent cannot easily interrupt or predict the full impact of.
From the tool's definition Tool name 'start_project_render' and description 'Start rendering the current project with optional preset and path' indicates execution of a rendering operation that triggers external processing (video encoding/rendering engine).
Documented attack patterns abuse exactly the kind of access start_project_render gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and DaVinci Resolve MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for start_project_render:
{
"version": "1",
"default": "deny",
"tools": {
"start_project_render": {
"limits": [
{
"counter": "start_project_render_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}start_project_render 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.
Start rendering the current project with optional preset and path. It is categorised as a Execute tool in the DaVinci Resolve MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the DaVinci Resolve MCP Server MCP server in PolicyLayer and add a rule for start_project_render: 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 Server. Nothing to install.
start_project_render 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 start_project_render 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 start_project_render. 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.
start_project_render is provided by the DaVinci Resolve MCP Server MCP server (tooflex/davinci-resolve-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from DaVinci Resolve MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
32 DaVinci Resolve MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.