Medium Risk

ti_load_version

Load a color version. Args: version_name: Name of the version. version_type: 0=Local, 1=Remote. Default: 0. item_index: 0-based item index. Default: 0.

How to control ti_load_version ↓

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

Medium Risk

Loading a color version applies a specific color grading state to a clip, which is a reversible modification to the project's color settings. It doesn't delete data or execute arbitrary code, making Write the most appropriate category.

From the tool's definition 'Load a color version' — loads/applies a named color version to a timeline item, modifying the active color state

Documented attack patterns abuse exactly the kind of access ti_load_version 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_load_version:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "ti_load_version": {
      "limits": [
        {
          "counter": "ti_load_version_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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

  1. Create a free account and register DaVinci Resolve MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
LIMIT THIS TOOL →

Free to start. No card required.

Go deeper

What does the ti_load_version tool do? +

Load a color version. Args: version_name: Name of the version. version_type: 0=Local, 1=Remote. Default: 0. item_index: 0-based item index. Default: 0. 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 ti_load_version? +

Register the DaVinci Resolve MCP server in PolicyLayer and add a rule for ti_load_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. Nothing to install.

What risk level is ti_load_version? +

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

Can I rate-limit ti_load_version? +

Yes. Add a rate_limit block to the ti_load_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.

How do I block ti_load_version completely? +

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

What MCP server provides ti_load_version? +

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

Enforce policy on every DaVinci Resolve MCP tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.