Render pipeline: jobs, presets, formats, codecs, and rendering. Actions: add_job() -> {job_id} delete_job(job_id) -> {success} delete_all_jobs() -> {success} list_jobs() -> {jobs} get_job_status(job_id) -> {status} start(job_ids?, interactive?) -> {success} stop() -> {success} is_rendering() -> {...
AI agents invoke render 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 executes rendering operations in video editing software, which triggers external computational processes that generate output files. While rendering itself is not destructive (the original timeline remains), it is an Execute category tool because it initiates complex external operations whose side effects (CPU usage, disk I/O, file generation) depend on the job configuration and parameters passed.
From the tool's definition The tool provides actions like start(), stop(), add_job(), delete_job(), and delete_all_jobs() that trigger rendering operations in DaVinci Resolve.
Documented attack patterns abuse exactly the kind of access render 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:
{
"version": "1",
"default": "deny",
"tools": {
"render": {
"limits": [
{
"counter": "render_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}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.
Render pipeline: jobs, presets, formats, codecs, and rendering. Actions: add_job() -> {job_id} delete_job(job_id) -> {success} delete_all_jobs() -> {success} list_jobs() -> {jobs} get_job_status(job_id) -> {status} start(job_ids?, interactive?) -> {success} stop() -> {success} is_rendering() -> {rendering} get_formats() -> {formats} get_codecs(format) -> {codecs} get_format_and_codec() -> {format, codec} set_format_and_codec(format, codec) -> {success} get_mode() -> {mode} set_mode(mode) -> {success} get_resolutions(format, codec) -> {resolutions} get_settings() -> {settings} (alias for set_render_settings with get) set_settings(settings) -> {success} list_presets() -> {presets} load_preset(name) -> {success} save_preset(name) -> {success} delete_preset(name) -> {success} quick_export_presets() -> {presets} quick_export(preset, params?) -> {status} render_capabilities() -> {methods, formats, presets, quick_export_presets} probe_render_matrix(formats?, max_pairs?) -> {matrix, errors} probe_render_settings() -> {format_and_codec, mode, settings, jobs, is_rendering} validate_render_settings(settings, require_temp_target?) -> {valid, errors, unknown_keys} safe_set_render_settings(settings, dry_run?, restore?, require_temp_target?) -> {success, diff} prepare_render_job(target_dir, settings?, format?, codec?, custom_name?, dry_run?) -> {success, job_id} render_job_lifecycle_probe(target_dir, settings?, format?, codec?, custom_name?) -> {success, job_id, status_before_delete} quick_export_capabilities() -> {presets, safe_params, guards} safe_quick_export(preset, target_dir?|params?, custom_name?, dry_run?, allow_render?) -> {success, status} export_render_boundary_report(include_matrix?, max_pairs?, include_quick_export?) -> {capabilities, settings, matrix?}. 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: 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 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 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. 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 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.