start_rendering_jobs

What start_rendering_jobs does on DaVinci Resolve MCP

AI agents invoke start_rendering_jobs 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 start_rendering_jobs is rated High

This tool executes rendering operations that initiate long-running external processes consuming CPU, GPU, and disk resources. While rendering is not destructive (it creates new files rather than deleting), it is an Execute action because it triggers complex external operations with side effects (resource consumption, file generation, timeline/workflow modifications) that cannot be easily undone or interrupted…

From the tool's definition Tool name 'start_rendering_jobs' and description 'Start rendering jobs' indicate the tool triggers external operations (rendering workflows in DaVinci Resolve) whose completion and resource consumption depend on arguments and system state.

The rule that runs start_rendering_jobs 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 start_rendering_jobs, this is the rule to start with:

{
  "version": "1",
  "default": "deny",
  "tools": {
    "start_rendering_jobs": {
      "limits": [
        {
          "counter": "start_rendering_jobs_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

Questions about start_rendering_jobs