Import/export render and burn-in presets. Actions: import_render(path) -> {success} export_render(name, path) -> {success} import_burnin(path) -> {success} export_burnin(name, path) -> {success}
AI agents use render_presets 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.
This tool modifies the application state by importing presets (creating or updating preset configurations) and exports data by writing files. These are reversible write operations. While export is read-like, the primary capability is importing presets which creates/modifies application data.
From the tool's definition The tool provides import/export actions: import_render(path), export_render(name, path), import_burnin(path), export_burnin(name, path). Import operations modify the presets stored in DaVinci Resolve by adding new configurations.
Documented attack patterns abuse exactly the kind of access render_presets 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 render_presets:
{
"version": "1",
"default": "deny",
"tools": {
"render_presets": {
"limits": [
{
"counter": "render_presets_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}render_presets 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.
Import/export render and burn-in presets. Actions: import_render(path) -> {success} export_render(name, path) -> {success} import_burnin(path) -> {success} export_burnin(name, path) -> {success}. 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 render_presets: 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.
render_presets 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 render_presets 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 render_presets. 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.
render_presets 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.