AI agents use resolve_node_set_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.
This tool modifies configuration state (cache mode) on a node within a grade. While reversible and not destructive, it constitutes a Write operation as it changes application state. The severity is medium because incorrect cache mode settings could impact rendering performance or cause unexpected re-computation, but the effect is not permanent and can be undone.
From the tool's definition 'Set the cache mode for a specific node in the current clip's grade' – this modifies node properties in a color grading workflow, changing cache behavior which affects how the node is processed and stored.
Attacks that exploit this kind of access
Set the cache mode for a specific node in the current clip's grade. 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.
Register the Resolve MCP server in PolicyLayer and add a rule for resolve_node_set_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.
resolve_node_set_cache 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 resolve_node_set_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.
Set action: deny in the PolicyLayer policy for resolve_node_set_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.
resolve_node_set_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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →