Set the render mode. Args: mode: 0 for Individual Clips, 1 for Single Clip.
AI agents use set_current_render_mode 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 application configuration (render mode preference) reversibly without executing external operations, deleting data, or creating side effects beyond the setting change itself. It falls under Write category as a configuration update. Severity is low because changing render mode preferences has limited blast radius—worst case is inefficient rendering behavior, not data loss or unintended operations.
From the tool's definition Tool sets/modifies the render mode configuration (mode: 0 or 1), changing application state. The name 'set_' indicates modification. The description shows this changes a preference/setting rather than executing a render job or deleting data.
Documented attack patterns abuse exactly the kind of access set_current_render_mode 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 set_current_render_mode:
{
"version": "1",
"default": "deny",
"tools": {
"set_current_render_mode": {
"limits": [
{
"counter": "set_current_render_mode_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}set_current_render_mode 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.
Set the render mode. Args: mode: 0 for Individual Clips, 1 for Single Clip. 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 set_current_render_mode: 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.
set_current_render_mode 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 set_current_render_mode 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 set_current_render_mode. 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.
set_current_render_mode 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.