Load a burn-in preset by name for the project. Args: preset_name: Name of the burn-in preset to load.
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.
Loading a burn-in preset modifies the project's active configuration/settings by applying a named preset. This is a reversible write operation — another preset can be loaded or the setting can be changed — so it falls under Write rather than Destructive. Misuse could affect render outputs but is recoverable.
From the tool's definition Load a burn-in preset by name for the project
Documented attack patterns abuse exactly the kind of access load_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 load_burn_in_preset:
{
"version": "1",
"default": "deny",
"tools": {
"load_burn_in_preset": {
"limits": [
{
"counter": "load_burn_in_preset_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}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.
Free to start. No card required.
Load a burn-in preset by name for the project. Args: preset_name: Name of the burn-in preset to load. 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.
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.
load_burn_in_preset is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
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.
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.
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.
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.