Medium Risk

set_cache_path

Set cache file path for the current project. Args: path_type: Type of cache path to set. Options: 'local', 'network' path: File system path for the cache

How to control set_cache_path ↓

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.

Medium Risk

This tool writes configuration data to the DaVinci Resolve project by setting where cache files are stored. While reversible (the cache path can be changed again), it modifies project state and could impact project stability or data organization if misconfigured.

From the tool's definition Tool modifies project configuration by setting cache file path through 'set_cache_path' with path_type and path parameters. This creates or changes cached files in the project, which is a reversible write operation.

Documented attack patterns abuse exactly the kind of access set_cache_path 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_cache_path:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "set_cache_path": {
      "limits": [
        {
          "counter": "set_cache_path_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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.

  1. Create a free account and register DaVinci Resolve MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
LIMIT THIS TOOL →

Free to start. No card required.

Go deeper

What does the set_cache_path tool do? +

Set cache file path for the current project. Args: path_type: Type of cache path to set. Options: 'local', 'network' path: File system path for the cache. 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.

How do I enforce a policy on set_cache_path? +

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.

What risk level is set_cache_path? +

set_cache_path is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit set_cache_path? +

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.

How do I block set_cache_path completely? +

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.

What MCP server provides set_cache_path? +

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.

Enforce policy on every DaVinci Resolve MCP tool call.

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.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.