Create a new node in the current Fusion composition.
AI agents use create_fusion_node to create or update resources in DaVinci Resolve MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your DaVinci Resolve MCP Server environment.
The tool creates new nodes in Fusion (DaVinci Resolve's visual effects engine), which modifies the project state reversibly. This is a Write operation: it creates new data structures that can be deleted or edited later.
From the tool's definition Tool description states 'Create a new node in the current Fusion composition' — this is a create operation that adds new elements to a project's visual effects graph.
Documented attack patterns abuse exactly the kind of access create_fusion_node gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and DaVinci Resolve MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for create_fusion_node:
{
"version": "1",
"default": "deny",
"tools": {
"create_fusion_node": {
"limits": [
{
"counter": "create_fusion_node_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_fusion_node 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.
Create a new node in the current Fusion composition. It is categorised as a Write tool in the DaVinci Resolve MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the DaVinci Resolve MCP Server MCP server in PolicyLayer and add a rule for create_fusion_node: 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 Server. Nothing to install.
create_fusion_node 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 create_fusion_node 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 create_fusion_node. 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.
create_fusion_node is provided by the DaVinci Resolve MCP Server MCP server (tooflex/davinci-resolve-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from DaVinci Resolve MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
32 DaVinci Resolve MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.