Delete a track from the timeline. Args: track_type: 'video', 'audio', or 'subtitle'. track_index: 1-based track index to delete.
AI agents call timeline_delete_track 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 track from a timeline in video editing software removes all clips, effects, and data associated with that track. This action cannot be undone programmatically by the tool itself and results in permanent loss of editorial work. This fits the Destructive category as it irreversibly removes data.
From the tool's definition Tool name is 'timeline_delete_track' and description states 'Delete a track from the timeline.' The use of 'delete' combined with removal of timeline track data represents irreversible data loss.
Documented attack patterns abuse exactly the kind of access timeline_delete_track 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 timeline_delete_track:
{
"version": "1",
"default": "deny",
"hide": [
"timeline_delete_track"
]
} timeline_delete_track 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 track from the timeline. Args: track_type: 'video', 'audio', or 'subtitle'. track_index: 1-based track index 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 timeline_delete_track: 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.
timeline_delete_track 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 timeline_delete_track 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 timeline_delete_track. 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.
timeline_delete_track 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.