New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

delete_render_job

Delete a specific render job by its ID.

SERVERDaVinci Resolve MCP SOURCEsamuelgursky/davinci-resolve-mcp
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

Questions about delete_render_job

What does the delete_render_job tool do? +

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.

How do I enforce a policy on delete_render_job? +

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.

What risk level is delete_render_job? +

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.

Can I rate-limit delete_render_job? +

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.

How do I block delete_render_job completely? +

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.

What MCP server provides delete_render_job? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of DaVinci Resolve's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.