Import a cloud project from a file. Mirrors ProjectManager.ImportCloudProject(filePath, {cloudSettings}). Args: file_path: absolute path to the cloud project file (required). project_name, project_media_path, is_collab, sync_mode, is_camera_access: cloudSettings dict keys; same semantics as creat...
AI agents use import_cloud_project_tool 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 tool modifies the DaVinci Resolve project state reversibly by importing cloud projects with associated metadata and collaboration settings. While it creates project resources, it does not irreversibly delete data (Destructive), execute arbitrary code (Execute), or move money (Financial).
From the tool's definition ImportCloudProject(filePath, {cloudSettings}) creates or modifies project state by importing a cloud project with settings like project_name, project_media_path, is_collab, sync_mode, is_camera_access.
Documented attack patterns abuse exactly the kind of access import_cloud_project_tool 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 import_cloud_project_tool:
{
"version": "1",
"default": "deny",
"tools": {
"import_cloud_project_tool": {
"limits": [
{
"counter": "import_cloud_project_tool_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}import_cloud_project_tool 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 cloud project from a file. Mirrors ProjectManager.ImportCloudProject(filePath, {cloudSettings}). Args: file_path: absolute path to the cloud project file (required). project_name, project_media_path, is_collab, sync_mode, is_camera_access: cloudSettings dict keys; same semantics as create_cloud_project_tool. 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_cloud_project_tool: 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_cloud_project_tool 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_cloud_project_tool 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_cloud_project_tool. 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_cloud_project_tool 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.