Rename a timeline item. Args: name: New timeline item name. item_index: 0-based item index. Default: 0. track_type: 'video' or 'audio'. Default: 'video'. track_index: 1-based track index. Default: 1.
AI agents use ti_set_name to create or update resources in DaVinci Resolve MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your DaVinci Resolve MCP environment.
Renaming a timeline item is a write operation that modifies metadata in the video project reversibly. The user can easily rename it back or to something else. This does not execute commands, delete data irreversibly, involve financial transactions, or pose significant risk. The blast radius is minimal as it only changes a label/name property of a timeline element, not the media itself or project structure.
From the tool's definition Tool description explicitly states 'Rename a timeline item' and accepts parameters for modifying the name of timeline items in DaVinci Resolve. This is a reversible data modification operation.
Documented attack patterns abuse exactly the kind of access ti_set_name 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_set_name:
{
"version": "1",
"default": "deny",
"tools": {
"ti_set_name": {
"limits": [
{
"counter": "ti_set_name_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}ti_set_name stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Rename a timeline item. Args: name: New timeline item name. item_index: 0-based item index. Default: 0. track_type: 'video' or 'audio'. Default: 'video'. track_index: 1-based track index. Default: 1. It is categorised as a Write tool in the DaVinci Resolve MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the DaVinci Resolve MCP server in PolicyLayer and add a rule for ti_set_name: 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_set_name is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the ti_set_name 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_set_name. 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_set_name 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.