resolve_export_burn_in_preset · Resolve MCP: Risk & Policy

WHAT IT DOES

What resolve_export_burn_in_preset does on Resolve

AI agents use resolve_export_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_export_burn_in_preset needs a policy

Exporting a preset to file creates or modifies data on disk in a reversible manner. This is a Write operation rather than Read (which would merely retrieve existing data) or higher severity categories. The blast radius is medium because an AI agent could export presets to unintended locations or overwrite existing presets, but the operation is reversible by deleting the file or restoring from backup.

From the tool's definition Tool name explicitly states 'export' and description indicates it writes/saves a burn-in preset 'to file', which is a create/modify operation that creates a new file artifact.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

resolve_export_burn_in_preset Rate-limited

resolve_export_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_export_burn_in_preset": {
      "limits": [
        {
          "counter": "resolve_export_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_export_burn_in_preset

What does the resolve_export_burn_in_preset tool do? +

Export a burn-in preset to file. 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_export_burn_in_preset? +

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

resolve_export_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_export_burn_in_preset? +

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

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

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