Medium Risk

set_track_name

Set the name of a track in the current timeline.

How to control set_track_name ↓

What set_track_name does on DaVinci Resolve MCP Server

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

Medium Risk

Why set_track_name needs a policy

This tool modifies project data (track naming) in a way that is easily reversible (the name can be changed again). It does not delete, execute external code, or cause irreversible changes. It fits the Write category as it creates or modifies data reversibly. The blast radius is minimal—renaming a track causes no cascading effects on media, effects, or project integrity.

From the tool's definition set_track_name performs a reversible modification operation on track metadata (the name/label of a timeline track). The description explicitly states it 'Set the name of a track', which is a create/update operation on data within DaVinci Resolve.

Documented attack patterns abuse exactly the kind of access set_track_name gives an agent:

How to control set_track_name

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_track_name:

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

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

  1. Create a free account and register DaVinci Resolve MCP Server — 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.

Related tools and policies

Go deeper

Questions about set_track_name

What does the set_track_name tool do? +

Set the name of a track in the current timeline. 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.

How do I enforce a policy on set_track_name? +

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

What risk level is set_track_name? +

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

Can I rate-limit set_track_name? +

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

How do I block set_track_name completely? +

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

What MCP server provides set_track_name? +

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

Enforce policy on every DaVinci Resolve MCP Server tool call.

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.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.