load_burn_in_preset

Load a burn-in preset by name for the project.

SERVERDaVinci Resolve MCP SOURCEsamuelgursky/davinci-resolve-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/samuelgursky-davinci-resolve-mcp/load-burn-in-preset.md

WHAT IT DOES

What load_burn_in_preset does on DaVinci Resolve MCP

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

RISK

Why load_burn_in_preset is rated Medium

Loading/applying a burn-in preset modifies the project's render/export settings by applying a named configuration. This is a reversible write operation — the preset can be changed or removed — affecting the project's output settings rather than destroying data or executing arbitrary code.

From the tool's definition Load a burn-in preset by name for the project

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs load_burn_in_preset safely

PolicyLayer is an MCP gateway: it sits between your AI agents and DaVinci Resolve MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For load_burn_in_preset, this is the rule to start with:

load_burn_in_preset Rate-limited

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": {
    "load_burn_in_preset": {
      "limits": [
        {
          "counter": "load_burn_in_preset_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect DaVinci Resolve MCP, apply this rule, and every load_burn_in_preset call is checked against it from then on.

FAQ

Questions about load_burn_in_preset

What does the load_burn_in_preset tool do? +

Load a burn-in preset by name for the project. It is categorised as a Write tool in the DaVinci Resolve MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on load_burn_in_preset? +

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

What risk level is load_burn_in_preset? +

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 load_burn_in_preset? +

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

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

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

KEEP EXPLORING

More on DaVinci Resolve, and thousands of servers like it.

This server

All 355 DaVinci Resolve tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →