set_current_database
Switch to a different database.
This record as markdown: /tools/samuelgursky-davinci-resolve-mcp/set-current-database.md
What set_current_database does on DaVinci Resolve MCP
AI agents use set_current_database 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 set_current_database is rated Medium
Switching databases is a reversible state change that affects which project/workspace is active. It is not a Read operation (no mere data retrieval), not Destructive (the change can be undone by switching back), not Execute in the command-execution sense, not Financial. It qualifies as Write because it modifies application configuration/state.
From the tool's definition Tool name is 'set_current_database' and description states 'Switch to a different database.' This changes the active database context, which modifies application state and can affect which project data is accessed and manipulated.
Attacks that exploit this kind of access
The rule that runs set_current_database 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 set_current_database, this is the rule to start with:
set_current_database 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 set_current_database call is checked against it from then on.
Questions about set_current_database
Switch to a different database. 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_database: 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_database 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_database 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_database. 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_database 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