Delete a take by index. Args: take_index: 1-based take index. item_index: 0-based item index. Default: 0.
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.
This tool permanently removes video take data from a media pool or project. Deletion is irreversible and represents data loss. An AI agent could inadvertently delete critical takes if given incorrect indices, destroying editorial work. This exceeds Write (which is reversible) and qualifies as Destructive per the classification rules.
From the tool's definition Tool name 'ti_delete_take' uses the verb 'delete'; description explicitly states 'Delete a take by index.' The action is irreversible—once a take is deleted from DaVinci Resolve, it cannot be recovered through normal tool operations.
Documented attack patterns abuse exactly the kind of access ti_delete_take 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 ti_delete_take:
{
"version": "1",
"default": "deny",
"hide": [
"ti_delete_take"
]
}ti_delete_take 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 take by index. Args: take_index: 1-based take index. item_index: 0-based item index. Default: 0. 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 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.
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.
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.
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.
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.
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.