import_project_from_file
Import a project from a .drp file.
This record as markdown: /tools/samuelgursky-davinci-resolve-mcp/import-project-from-file.md
What import_project_from_file does on DaVinci Resolve MCP
AI agents use import_project_from_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.
Why import_project_from_file is rated Medium
Importing a project file modifies the application state by loading an external project into the editor. This is reversible (user can undo or switch projects) and does not permanently delete or overwrite existing data.
From the tool's definition Tool name 'import_project_from_file' indicates importing/loading a project file (.drp), which creates or modifies the current project state in DaVinci Resolve. The description confirms file-based project import.
Attacks that exploit this kind of access
The rule that runs import_project_from_file 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 import_project_from_file, this is the rule to start with:
import_project_from_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.
The button opens the PolicyLayer dashboard: create your workspace, connect DaVinci Resolve MCP, apply this rule, and every import_project_from_file call is checked against it from then on.
Questions about import_project_from_file
Import a project from a .drp file. 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 import_project_from_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.
import_project_from_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 import_project_from_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 import_project_from_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.
import_project_from_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.
More on DaVinci Resolve, and thousands of servers like it.
This server
Across the catalogue