resolve_set_current_timecode · Resolve MCP: Risk & Policy

WHAT IT DOES

What resolve_set_current_timecode does on Resolve

AI agents invoke resolve_set_current_timecode to trigger actions in Resolve. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why resolve_set_current_timecode needs a policy

This tool controls the playhead position in DaVinci Resolve, which is an external application operation. It doesn't merely read data, nor does it create/modify/delete content — it triggers a navigation/transport action in the external software. Misuse could disrupt editing workflows but has limited blast radius as it's reversible by moving the playhead back.

From the tool's definition 'Set the playhead to a specific timecode' — triggers an external operation in DaVinci Resolve that moves the playhead position

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

resolve_set_current_timecode Rate-limited

resolve_set_current_timecode stays usable, but rate-capped — a runaway agent can't fire it dozens of times 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_current_timecode": {
      "limits": [
        {
          "counter": "resolve_set_current_timecode_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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_current_timecode

What does the resolve_set_current_timecode tool do? +

Set the playhead to a specific timecode. It is categorised as a Execute tool in the Resolve MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on resolve_set_current_timecode? +

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

resolve_set_current_timecode is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit resolve_set_current_timecode? +

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

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

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