open_settings
Open the Project Settings dialog in DaVinci Resolve.
This record as markdown: /tools/samuelgursky-davinci-resolve-mcp/open-settings.md
What open_settings does on DaVinci Resolve MCP
AI agents invoke open_settings to trigger actions in DaVinci Resolve MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why open_settings is rated High
This tool triggers an external UI action within DaVinci Resolve — opening a dialog window. It doesn't purely read data (it causes a side effect in the application's UI state), nor does it write/modify data directly. It's best classified as Execute since it triggers an external operation (UI interaction) in the video editing software. Severity is low as opening a settings dialog has minimal blast radius on its own.
From the tool's definition Open the Project Settings dialog in DaVinci Resolve
Attacks that exploit this kind of access
The rule that runs open_settings 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 open_settings, this is the rule to start with:
open_settings stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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 open_settings call is checked against it from then on.
Questions about open_settings
Open the Project Settings dialog in DaVinci Resolve. It is categorised as a Execute tool in the DaVinci Resolve MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the DaVinci Resolve MCP server in PolicyLayer and add a rule for open_settings: 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.
open_settings is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the open_settings 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 open_settings. 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.
open_settings 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.
Across the catalogue