Delete a specific render job by its ID. Args: job_id: The unique ID of the render job to delete.
AI agents call delete_render_job to permanently remove resources in DaVinci Resolve MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting a render job is an irreversible operation that destroys work product (queued video rendering tasks). While not as severe as deleting media files, render jobs represent computational work and scheduling state that cannot be undone. This falls under the Destructive category per the rule that delete operations are irreversible.
From the tool's definition Tool name is 'delete_render_job' and description states 'Delete a specific render job by its ID.' The verb 'delete' combined with permanent removal of a render job constitutes an irreversible action.
Documented attack patterns abuse exactly the kind of access delete_render_job 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 delete_render_job:
{
"version": "1",
"default": "deny",
"hide": [
"delete_render_job"
]
}delete_render_job disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Delete a specific render job by its ID. Args: job_id: The unique ID of the render job to delete. It is categorised as a Destructive tool in the DaVinci Resolve MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the DaVinci Resolve MCP server in PolicyLayer and add a rule for delete_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.
delete_render_job is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_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 delete_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.
delete_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.
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.