Archive a project to a file with optional media. Args: project_name: Name of the project to archive. archive_path: Absolute path for the archive file (.dra). archive_src_media: Include source media in archive. Default: True. archive_render_cache: Include render cache. Default: True. archive_proxy...
AI agents use archive_project 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 creates new files and aggregates project data into an archive format. While archiving is reversible (the archive can be deleted or re-exported), it writes and persists data to disk. This is a Write operation rather than Destructive because archiving doesn't irreversibly delete or overwrite existing project data—it creates a copy in archive format.
From the tool's definition The tool archives a project to a file with optional media inclusion. The description states it creates an archive file (.dra), which is a data export/write operation that persists data to a new file location.
Documented attack patterns abuse exactly the kind of access archive_project 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 archive_project:
{
"version": "1",
"default": "deny",
"tools": {
"archive_project": {
"limits": [
{
"counter": "archive_project_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}archive_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.
Archive a project to a file with optional media. Args: project_name: Name of the project to archive. archive_path: Absolute path for the archive file (.dra). archive_src_media: Include source media in archive. Default: True. archive_render_cache: Include render cache. Default: True. archive_proxy_media: Include proxy media. Default: False. 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 archive_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.
archive_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 archive_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 archive_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.
archive_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.
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.