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

ti_delete_take

Delete a take by index.

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/ti-delete-take.md

What ti_delete_take does on DaVinci Resolve MCP

AI agents call ti_delete_take 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 ti_delete_take is rated Critical

The tool performs an irreversible deletion of a take (a recorded video segment), which cannot be undone through normal means. This matches the Destructive category definition: 'irreversibly deletes or overwrites data, or actions that cannot be undone (delete, drop, purge, force-push).' While the blast radius is limited to a single take rather than an entire project, accidental deletion of takes during video editing…

From the tool's definition Tool name contains 'delete' and description states 'Delete a take by index' - this is an explicit deletion operation that irreversibly removes data from the video editing project.

Questions about ti_delete_take

What does the ti_delete_take tool do? +

Delete a take by index. 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 ti_delete_take? +

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

ti_delete_take 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 ti_delete_take? +

Yes. Add a rate_limit block to the ti_delete_take 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 ti_delete_take completely? +

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

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