resolve_load_burn_in_preset · Resolve MCP: Risk & Policy

WHAT IT DOES

What resolve_load_burn_in_preset does on Resolve

AI agents use resolve_load_burn_in_preset 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_load_burn_in_preset needs a policy

Loading a burn-in preset applies visual/data overlay settings to a clip, constituting a Write operation (modifying clip state). The blast radius is medium because it affects timeline rendering/appearance but is reversible; the change can be undone and doesn't delete data or execute arbitrary code. It's more severe than a pure Read but less severe than Destructive or Execute actions.

From the tool's definition Tool description states 'Load a data burn-in preset for a timeline clip' — this modifies clip properties by applying a preset, which is a reversible configuration change to the timeline.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

resolve_load_burn_in_preset Rate-limited

resolve_load_burn_in_preset 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_load_burn_in_preset": {
      "limits": [
        {
          "counter": "resolve_load_burn_in_preset_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_load_burn_in_preset

What does the resolve_load_burn_in_preset tool do? +

Load a data burn-in preset for a timeline clip. 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_load_burn_in_preset? +

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

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

Can I rate-limit resolve_load_burn_in_preset? +

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

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

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