AI agents use import_project to create or update resources in DaVinci Resolve MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your DaVinci Resolve MCP Server environment.
Importing a project is a reversible write operation that adds or modifies data within the application. It is not a destructive delete operation, does not execute arbitrary code or commands, and does not involve financial transactions. While it involves reading from an external file, the primary effect is creating/modifying project state in the resolve application.
From the tool's definition Tool name 'import_project' and description 'Import a project from a file' indicate file-based data ingestion that creates or modifies project state in DaVinci Resolve Studio.
Documented attack patterns abuse exactly the kind of access import_project gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and DaVinci Resolve MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for import_project:
{
"version": "1",
"default": "deny",
"tools": {
"import_project": {
"limits": [
{
"counter": "import_project_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}import_project 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.
Import a project from a file. It is categorised as a Write tool in the DaVinci Resolve MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the DaVinci Resolve MCP Server MCP server in PolicyLayer and add a rule for import_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 Server. Nothing to install.
import_project 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 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. 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 is provided by the DaVinci Resolve MCP Server MCP server (tooflex/davinci-resolve-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from DaVinci Resolve MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
32 DaVinci Resolve MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.