// MCP TOOL REFERENCE

start_rendering_jobs

ServerDaVinci Resolve MCP
CategoryExecute

WHAT START_RENDERING_JOBS ON DAVINCI RESOLVE MCP DOES

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.

THE RISK

High Risk

This tool executes rendering operations on video projects, which are complex external processes triggered by the AI agent. While not destructive (rendering doesn't delete data) and not financial, it is Execute-category because it initiates external operations whose outcomes and side effects depend on the specified arguments.

From the tool's definition Tool name 'start_rendering_jobs' and description 'Start rendering jobs' directly triggers external operations (video rendering) whose effects depend on arguments (job_ids, is_interactive_mode).

Documented attack patterns abuse exactly the kind of access start_rendering_jobs gives an agent:

HOW TO CONTROL START_RENDERING_JOBS

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 start_rendering_jobs:

policy.json

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

start_rendering_jobs 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.

Create a free account and register DaVinci Resolve MCP — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

More DaVinci Resolve MCP tools

Destructive clear_clip_flags Clear flags on a clip. Args: clip_id: Unique ID of the clip. color: S Destructive clear_clip_transcription Clear transcription for a specific clip. Args: clip_id: Unique ID of the clip Destructive clear_folder_transcription Clear audio transcription for all clips in a folder. Args: folder_name: N Destructive clear_transcription Clear audio transcription for a clip. Args: clip_name: Name of the clip t Destructive dctl Author and install DCTL files (Color page custom shaders + ACES transforms). Regular Destructive delete_clip_marker_at_frame Delete a marker at a specific frame on a clip. Args: clip_id: Unique ID of th Destructive delete_clip_marker_by_custom_data Delete a marker by its custom data string. Args: clip_id: Unique ID of the cl Destructive delete_clip_markers_by_color Delete all markers of a specific color on a clip. Args: clip_id: Unique ID of

All 369 DaVinci Resolve MCP tools →

Execute tools on other servers

Frida Game Hacking MCP remove_breakpoint Procmon request_elevation WireMCP capture_packets Pentest Ai run_probe

Go deeper

High-risk tools in DaVinci Resolve MCP → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

What does the start_rendering_jobs tool do? +

Start rendering jobs. If no job IDs specified, renders all queued jobs. Args: job_ids: Optional list of job IDs to render. If None, renders all. is_interactive_mode: If True, enables interactive rendering mode. 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.

How do I enforce a policy on start_rendering_jobs? +

Register the DaVinci Resolve MCP server in PolicyLayer and add a rule for start_rendering_jobs: 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.

What risk level is start_rendering_jobs? +

start_rendering_jobs is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit start_rendering_jobs? +

Yes. Add a rate_limit block to the start_rendering_jobs 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.

How do I block start_rendering_jobs completely? +

Set action: deny in the PolicyLayer policy for start_rendering_jobs. 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.

What MCP server provides start_rendering_jobs? +

start_rendering_jobs 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.

Enforce policy on every DaVinci Resolve MCP tool call.

Deterministic rules across all 369 DaVinci Resolve MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

GOVERN DAVINCI RESOLVE →

Free to start. No card required.

369 DaVinci Resolve MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

start_rendering_jobs

// WHAT START_RENDERING_JOBS ON DAVINCI RESOLVE MCP DOES

// THE RISK

// HOW TO CONTROL START_RENDERING_JOBS

// EXPLORE