Set the current version for a clip by name (e.g., switch between color grades).
AI agents use set_current_version to create or update resources in DaVinci Resolve MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your DaVinci Resolve MCP Server environment.
This tool modifies project state by changing which version of a clip is active (e.g., selecting between different color grades). This is a Write operation because it changes data reversibly — the previous version remains available and can be switched back to. It does not execute arbitrary code, delete data irreversibly, or involve financial transactions.
From the tool's definition Tool description states 'Set the current version for a clip by name (e.g., switch between color grades)' — this modifies the state of a clip's version assignment, which is a reversible change to project data.
Documented attack patterns abuse exactly the kind of access set_current_version gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and DaVinci Resolve MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for set_current_version:
{
"version": "1",
"default": "deny",
"tools": {
"set_current_version": {
"limits": [
{
"counter": "set_current_version_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} set_current_version 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.
Set the current version for a clip by name (e.g., switch between color grades). It is categorised as a Write tool in the DaVinci Resolve MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the DaVinci Resolve MCP Server MCP server in PolicyLayer and add a rule for set_current_version: 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 Server. Nothing to install.
set_current_version 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 set_current_version 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 set_current_version. 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.
set_current_version is provided by the DaVinci Resolve MCP Server MCP server (tooflex/davinci-resolve-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from DaVinci Resolve MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
32 DaVinci Resolve MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.