resolve_set_track_name · Resolve MCP: Risk & Policy

WHAT IT DOES

What resolve_set_track_name does on Resolve

AI agents use resolve_set_track_name to create or update resources in Resolve — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Resolve environment.

WHY IT NEEDS A POLICY

Why resolve_set_track_name needs a policy

This tool modifies metadata (track name) on a timeline in a reversible manner. The change can be undone by renaming the track again to its previous name or any other name. It does not execute code, delete data, or create financial obligations. It is Write rather than Read because it mutates state (the track name) rather than only querying it.

From the tool's definition Tool description explicitly states 'Rename a track' which is a modification operation. The verb 'Rename' and 'set' indicate creation or modification of metadata on an existing track, not data deletion or irreversible destruction.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

resolve_set_track_name Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "resolve_set_track_name": {
      "limits": [
        {
          "counter": "resolve_set_track_name_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Resolve, so you can run agents against it safely.

FAQ

Questions about resolve_set_track_name

What does the resolve_set_track_name tool do? +

Rename a track on the current timeline. It is categorised as a Write tool in the Resolve MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on resolve_set_track_name? +

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

What risk level is resolve_set_track_name? +

resolve_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 resolve_set_track_name? +

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

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

resolve_set_track_name is provided by the Resolve MCP server (jenkinsm13/resolve-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.