New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

set_current_database

Switch to a different database.

SERVERDaVinci Resolve MCP SOURCEsamuelgursky/davinci-resolve-mcp
Medium RISK CLASS
Category Write
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

Questions about set_current_database

What does the set_current_database tool do? +

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.

How do I enforce a policy on set_current_database? +

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.

What risk level is set_current_database? +

set_current_database is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit set_current_database? +

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.

How do I block set_current_database completely? +

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.

What MCP server provides set_current_database? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of DaVinci Resolve's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.