set_cache_path
Set cache file path for the current project.
This record as markdown: /tools/samuelgursky-davinci-resolve-mcp/set-cache-path.md
What set_cache_path does on DaVinci Resolve MCP
AI agents use set_cache_path 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_cache_path is rated Medium
This tool creates or modifies project metadata/settings (the cache path configuration) rather than media content itself. While reversible (a new path can be set), it changes project state and could affect project functionality if misconfigured (e.g., pointing to invalid or inaccessible locations). It does not execute arbitrary code, delete data irreversibly, or handle finances, placing it in the Write category.
From the tool's definition The tool 'set_cache_path' modifies project settings by changing where cache files are stored ('Set cache file path for the current project'). This is a configuration modification that affects the project state.
Attacks that exploit this kind of access
The rule that runs set_cache_path 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_cache_path, this is the rule to start with:
set_cache_path 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_cache_path call is checked against it from then on.
Questions about set_cache_path
Set cache file path for 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_cache_path: 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_cache_path 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_cache_path 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_cache_path. 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_cache_path 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