Rename the current project. Args: name: New name for the project.
AI agents use set_project_name 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 project metadata (the project name) but does not create, delete, or destroy data—only changes an attribute. The operation is fully reversible by renaming again. This is a classic Write operation (create/modify data reversibly). Severity is low because renaming a project has minimal blast radius; it affects only the project identifier, not its content or dependencies, and can be easily undone.
From the tool's definition The tool 'set_project_name' renames the current project, which is a reversible metadata modification. The description explicitly states 'Rename the current project' with an argument 'name: New name for the project.'
Documented attack patterns abuse exactly the kind of access set_project_name 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 set_project_name:
{
"version": "1",
"default": "deny",
"tools": {
"set_project_name": {
"limits": [
{
"counter": "set_project_name_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}set_project_name 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.
Rename the current project. Args: name: New name for the project. 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 set_project_name: 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.
set_project_name 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 set_project_name 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 set_project_name. 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.
set_project_name 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.