delete_render_job
Delete a specific render job by its ID.
This record as markdown: /tools/samuelgursky-davinci-resolve-mcp/delete-render-job.md
What delete_render_job does on DaVinci Resolve MCP
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.
Why delete_render_job is rated Critical
Deleting a render job removes queued or completed rendering work that cannot be trivially recovered. This is an irreversible operation that destroys state in the DaVinci Resolve application.
From the tool's definition Tool name and description: 'Delete a specific render job by its ID' — the verb 'delete' combined with the action of removing a render job by identifier indicates irreversible removal of data/state.
Attacks that exploit this kind of access
The rule that runs delete_render_job 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 delete_render_job, this is the rule to start with:
delete_render_job is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect DaVinci Resolve MCP, apply this rule, and every delete_render_job call is checked against it from then on.
Questions about delete_render_job
Delete a specific render job by its ID. 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.
More on DaVinci Resolve, and thousands of servers like it.
Across the catalogue