goto_root_project_folder
Navigate to the root project folder.
This record as markdown: /tools/samuelgursky-davinci-resolve-mcp/goto-root-project-folder.md
What goto_root_project_folder does on DaVinci Resolve MCP
AI agents invoke goto_root_project_folder to trigger actions in DaVinci Resolve MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why goto_root_project_folder is rated High
This tool triggers a navigation action within DaVinci Resolve (changing the active folder context), which is an external operation with side effects on the application state. It doesn't read, write, or delete data, but executes a UI/application-level action. Severity is low as the blast radius of navigating to root folder is minimal.
From the tool's definition Navigate to the root project folder
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs goto_root_project_folder 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 goto_root_project_folder, this is the rule to start with:
goto_root_project_folder stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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 goto_root_project_folder call is checked against it from then on.
Questions about goto_root_project_folder
Navigate to the root project folder. It is categorised as a Execute tool in the DaVinci Resolve MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the DaVinci Resolve MCP server in PolicyLayer and add a rule for goto_root_project_folder: 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.
goto_root_project_folder is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the goto_root_project_folder 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 goto_root_project_folder. 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.
goto_root_project_folder 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.
Across the catalogue