Manage DaVinci Resolve project databases. Actions: get_current() -> {db_type, db_name} list() -> {databases} set_current(db_info) -> {success} — db_info: {DbType, DbName}
AI agents use project_manager_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.
The set_current() action constitutes a reversible modification of application configuration state (the current active database). While not destructive in itself, it alters the context for all downstream operations and could lead to unintended modifications of different projects if an AI agent selects the wrong database.
From the tool's definition Tool provides 'set_current(db_info)' action that changes the active project database. This modifies application state and potentially redirects all subsequent operations to a different database context.
Documented attack patterns abuse exactly the kind of access project_manager_database 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 project_manager_database:
{
"version": "1",
"default": "deny",
"tools": {
"project_manager_database": {
"limits": [
{
"counter": "project_manager_database_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}project_manager_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.
Free to start. No card required.
Manage DaVinci Resolve project databases. Actions: get_current() -> {db_type, db_name} list() -> {databases} set_current(db_info) -> {success} — db_info: {DbType, DbName}. 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 project_manager_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.
project_manager_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 project_manager_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 project_manager_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.
project_manager_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.
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.