Save the current project. Note that DaVinci Resolve typically auto-saves projects, so this may not be necessary.
AI agents use save_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.
Saving a project persists changes to the project file, which is a reversible write operation. While not destructive (data can be further modified or reverted via version history), it commits the current state and could overwrite previous unsaved changes.
From the tool's definition Tool name 'save_project' and description 'Save the current project' indicates modification/persistence of project state. The note about auto-saves confirms this tool modifies stored data.
Documented attack patterns abuse exactly the kind of access save_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 save_project:
{
"version": "1",
"default": "deny",
"tools": {
"save_project": {
"limits": [
{
"counter": "save_project_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}save_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.
Save the current project. Note that DaVinci Resolve typically auto-saves projects, so this may not be necessary. 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 save_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.
save_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 save_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 save_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.
save_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.