Enable or disable a node. Args: node_index: 1-based node index. is_enabled: True to enable, False to disable. item_index: 0-based timeline item index. Default: 0. track_type: 'video' or 'audio'. Default: 'video'. track_index: 1-based track index. Default: 1.
AI agents use graph_set_node_enabled 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.
The tool modifies node states within the DaVinci Resolve editing environment, which affects how clips are processed but does not delete data or execute arbitrary code. The change is reversible (nodes can be re-enabled or disabled), classifying it as Write rather than Execute or Destructive.
From the tool's definition Tool description states 'Enable or disable a node' with boolean parameter 'is_enabled'. This modifies the state of video/audio processing nodes in the timeline—a reversible change to the editing workflow.
Documented attack patterns abuse exactly the kind of access graph_set_node_enabled 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 graph_set_node_enabled:
{
"version": "1",
"default": "deny",
"tools": {
"graph_set_node_enabled": {
"limits": [
{
"counter": "graph_set_node_enabled_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}graph_set_node_enabled 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.
Free to start. No card required.
Enable or disable a node. Args: node_index: 1-based node index. is_enabled: True to enable, False to disable. item_index: 0-based timeline item index. Default: 0. track_type: 'video' or 'audio'. Default: 'video'. track_index: 1-based track index. Default: 1. 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 graph_set_node_enabled: 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.
graph_set_node_enabled 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 graph_set_node_enabled 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 graph_set_node_enabled. 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.
graph_set_node_enabled 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.
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.