resolve_set_fusion_cache · Resolve MCP: Risk & Policy

WHAT IT DOES

What resolve_set_fusion_cache does on Resolve

AI agents use resolve_set_fusion_cache to create or update resources in Resolve — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Resolve environment.

WHY IT NEEDS A POLICY

Why resolve_set_fusion_cache needs a policy

This tool modifies clip properties (cache mode) within a DaVinci Resolve timeline, which is a reversible write operation. Cache mode changes affect rendering behavior and disk usage but do not delete data or execute arbitrary code. The blast radius is medium because incorrect cache settings could impact project performance or storage, but changes can be undone by resetting cache mode.

From the tool's definition Tool name 'resolve_set_fusion_cache' and description 'Set the Fusion Output Cache mode for a timeline clip' indicate modification of cache settings for a clip. The verb 'Set' denotes writing/modifying configuration state.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

resolve_set_fusion_cache Rate-limited

resolve_set_fusion_cache 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "resolve_set_fusion_cache": {
      "limits": [
        {
          "counter": "resolve_set_fusion_cache_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Resolve, so you can run agents against it safely.

FAQ

Questions about resolve_set_fusion_cache

What does the resolve_set_fusion_cache tool do? +

Set the Fusion Output Cache mode for a timeline clip. It is categorised as a Write tool in the Resolve MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on resolve_set_fusion_cache? +

Register the Resolve MCP server in PolicyLayer and add a rule for resolve_set_fusion_cache: 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 Resolve. Nothing to install.

What risk level is resolve_set_fusion_cache? +

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

Can I rate-limit resolve_set_fusion_cache? +

Yes. Add a rate_limit block to the resolve_set_fusion_cache 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 resolve_set_fusion_cache completely? +

Set action: deny in the PolicyLayer policy for resolve_set_fusion_cache. 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 resolve_set_fusion_cache? +

resolve_set_fusion_cache is provided by the Resolve MCP server (jenkinsm13/resolve-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.