set_project_name
Rename the current project.
This record as markdown: /tools/samuelgursky-davinci-resolve-mcp/set-project-name.md
What set_project_name does on DaVinci Resolve MCP
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.
Why set_project_name is rated Medium
This tool creates or modifies project metadata reversibly. While renaming a project is a modification, it does not delete data, execute arbitrary code, move financial resources, or trigger irreversible consequences. The blast radius is limited to project naming—an AI agent could create confusing project names but could rename them back. This is properly categorized as Write rather than Execute or Destructive.
From the tool's definition The tool's description states it renames the current project, which modifies the project metadata. The tool name 'set_project_name' and description 'Rename the current project' directly indicate a write operation that changes project state.
Attacks that exploit this kind of access
The rule that runs set_project_name safely
PolicyLayer is an MCP gateway: it sits between your AI agents and DaVinci Resolve MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For set_project_name, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect DaVinci Resolve MCP, apply this rule, and every set_project_name call is checked against it from then on.
Questions about set_project_name
Rename the current 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.
More on DaVinci Resolve, and thousands of servers like it.
This server
Across the catalogue