import_render_preset
Import a render preset from a file.
This record as markdown: /tools/samuelgursky-davinci-resolve-mcp/import-render-preset.md
What import_render_preset does on DaVinci Resolve MCP
AI agents use import_render_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.
Why import_render_preset is rated Medium
Importing a render preset modifies the application's available rendering configurations, which is a reversible write operation. While it reads from a file, the primary effect is to create/add new render preset data into the system. This is not destructive (presets can be removed), not financial, and not execute (it doesn't run code or trigger rendering itself).
From the tool's definition Tool name 'import_render_preset' and description 'Import a render preset from a file' indicates creating or modifying render configuration data within DaVinci Resolve by reading external preset files and installing them into the application state.
Attacks that exploit this kind of access
The rule that runs import_render_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 import_render_preset, this is the rule to start with:
import_render_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.
The button opens the PolicyLayer dashboard: create your workspace, connect DaVinci Resolve MCP, apply this rule, and every import_render_preset call is checked against it from then on.
Questions about import_render_preset
Import a render preset from a 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.
Register the DaVinci Resolve MCP server in PolicyLayer and add a rule for import_render_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.
import_render_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 import_render_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 import_render_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.
import_render_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.
More on DaVinci Resolve, and thousands of servers like it.
This server
Across the catalogue