Medium Risk

import_burn_in_preset

Import a burn-in preset from a file. Args: preset_path: Absolute path to the burn-in preset file.

How to control import_burn_in_preset ↓

AI agents use import_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.

Medium Risk

This tool imports a burn-in preset file into the video editing project, which constitutes creation or modification of project data (a burn-in overlay configuration applied to media). It is reversible (the preset can be removed or replaced), making it Write rather than Destructive.

From the tool's definition 'Import a burn-in preset from a file' - imports and applies a preset configuration to DaVinci Resolve, modifying project state and settings.

Documented attack patterns abuse exactly the kind of access import_burn_in_preset gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and DaVinci Resolve MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for import_burn_in_preset:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "import_burn_in_preset": {
      "limits": [
        {
          "counter": "import_burn_in_preset_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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

  1. Create a free account and register DaVinci Resolve MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
LIMIT THIS TOOL →

Free to start. No card required.

Go deeper

What does the import_burn_in_preset tool do? +

Import a burn-in preset from a file. Args: preset_path: Absolute path to the burn-in preset file. 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 import_burn_in_preset? +

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

import_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 import_burn_in_preset? +

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

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

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

Enforce policy on every DaVinci Resolve MCP tool call.

Deterministic rules across all 369 DaVinci Resolve MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

369 DaVinci Resolve MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.