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

set_current_timeline

Switch to a timeline by name.

SERVERDaVinci Resolve MCP SOURCEsamuelgursky/davinci-resolve-mcp
Medium RISK CLASS
Category Write
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/samuelgursky-davinci-resolve-mcp/set-current-timeline.md

What set_current_timeline does on DaVinci Resolve MCP

AI agents use set_current_timeline 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.

Why set_current_timeline is rated Medium

This tool changes the active/current timeline in DaVinci Resolve. It modifies application state by switching context to a different timeline, which is a reversible write operation (you can switch back). It does not delete data or execute code, but it does alter the working state of the editing session, which could affect subsequent operations performed by an AI agent.

From the tool's definition Switch to a timeline by name

Questions about set_current_timeline

What does the set_current_timeline tool do? +

Switch to a timeline by name. 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.

How do I enforce a policy on set_current_timeline? +

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

set_current_timeline is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit set_current_timeline? +

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

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

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