New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

goto_root_project_folder

Navigate to the root project folder.

SERVERDaVinci Resolve MCP SOURCEsamuelgursky/davinci-resolve-mcp
High RISK CLASS
Category Execute
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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

Questions about goto_root_project_folder

What does the goto_root_project_folder tool do? +

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.

How do I enforce a policy on goto_root_project_folder? +

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.

What risk level is goto_root_project_folder? +

goto_root_project_folder is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit goto_root_project_folder? +

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.

How do I block goto_root_project_folder completely? +

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.

What MCP server provides goto_root_project_folder? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of DaVinci Resolve's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.