ti_clear_flags
Clear flags from a timeline item.
This record as markdown: /tools/samuelgursky-davinci-resolve-mcp/ti-clear-flags.md
What ti_clear_flags does on DaVinci Resolve MCP
AI agents call ti_clear_flags 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_clear_flags is rated Critical
Clearing flags removes metadata markers from a timeline item. While not catastrophic, this action deletes existing flag data and cannot be easily undone, making it Destructive rather than Write. The blast radius is medium as it affects project metadata but not raw media files.
From the tool's definition 'Clear flags from a timeline item' — removing/clearing flags is an irreversible deletion of metadata annotations on a timeline item
Attacks that exploit this kind of access
The rule that runs ti_clear_flags 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 ti_clear_flags, this is the rule to start with:
ti_clear_flags 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 ti_clear_flags call is checked against it from then on.
Questions about ti_clear_flags
Clear flags from a timeline item. 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_clear_flags: 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_clear_flags 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_clear_flags 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_clear_flags. 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_clear_flags 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