close_project
Close the current project.
This record as markdown: /tools/samuelgursky-davinci-resolve-mcp/close-project.md
What close_project does on DaVinci Resolve MCP
AI agents call close_project to permanently remove resources in DaVinci Resolve MCP, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why close_project is rated Critical
Closing a project in a video editing application like DaVinci Resolve can result in loss of unsaved edits, which is not easily recoverable. While closing itself is not a delete operation, the potential for irreversible data loss places it closer to Destructive than Write.
From the tool's definition 'Close the current project' — closing a project without saving may result in irreversible loss of unsaved changes to the editing workflow
Attacks that exploit this kind of access
The rule that runs close_project 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 close_project, this is the rule to start with:
close_project is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect DaVinci Resolve MCP, apply this rule, and every close_project call is checked against it from then on.
Questions about close_project
Close the current project. It is categorised as a Destructive tool in the DaVinci Resolve MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the DaVinci Resolve MCP server in PolicyLayer and add a rule for close_project: 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.
close_project is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the close_project 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 close_project. 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.
close_project 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