Export a project to a .drp file. Args: project_name: Name of the project to export. file_path: Absolute path for the exported .drp file. with_stills_and_luts: Include stills and LUTs in export. Default: True.
AI agents use export_project_to_file 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.
This is a Write operation—it creates or modifies data reversibly by generating a new .drp export file at a specified path. While it persists data to disk, the operation is reversible (the export file can be deleted, and the original project remains intact). It does not delete, execute arbitrary code, or move financial resources.
From the tool's definition Tool exports a project to a .drp file, creating a new file on disk with user-specified content. Description explicitly states 'Export a project to a .drp file' with parameters for file_path and optional inclusion of stills/LUTs, indicating file…
Documented attack patterns abuse exactly the kind of access export_project_to_file 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 export_project_to_file:
{
"version": "1",
"default": "deny",
"tools": {
"export_project_to_file": {
"limits": [
{
"counter": "export_project_to_file_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}export_project_to_file 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.
Export a project to a .drp file. Args: project_name: Name of the project to export. file_path: Absolute path for the exported .drp file. with_stills_and_luts: Include stills and LUTs in export. Default: True. 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 export_project_to_file: 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.
export_project_to_file 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 export_project_to_file 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 export_project_to_file. 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.
export_project_to_file 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.