fuse_plugin

WHAT FUSE_PLUGIN ON DAVINCI RESOLVE MCP DOES

AI agents invoke fuse_plugin to trigger actions in DaVinci Resolve MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

THE RISK

High Risk

This tool installs executable Lua plugin code (.fuse files) into the Fusion/DaVinci Resolve environment. Installing plugins constitutes code execution at the application level — arbitrary Lua code is written to disk and loaded by the host application at startup or reload.

From the tool's definition Author and install Fusion Fuse plugins (.fuse files). Fuses are Lua plugins (or GLSL view-LUT shaders) that Fusion loads at startup.

Documented attack patterns abuse exactly the kind of access fuse_plugin gives an agent:

HOW TO CONTROL FUSE_PLUGIN

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 fuse_plugin:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "fuse_plugin": {
      "limits": [
        {
          "counter": "fuse_plugin_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

fuse_plugin stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

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

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

More DaVinci Resolve MCP tools

Destructive clear_clip_flags Clear flags on a clip. Args: clip_id: Unique ID of the clip. color: S Destructive clear_clip_transcription Clear transcription for a specific clip. Args: clip_id: Unique ID of the clip Destructive clear_folder_transcription Clear audio transcription for all clips in a folder. Args: folder_name: N Destructive clear_transcription Clear audio transcription for a clip. Args: clip_name: Name of the clip t Destructive dctl Author and install DCTL files (Color page custom shaders + ACES transforms). Regular Destructive delete_clip_marker_at_frame Delete a marker at a specific frame on a clip. Args: clip_id: Unique ID of th Destructive delete_clip_marker_by_custom_data Delete a marker by its custom data string. Args: clip_id: Unique ID of the cl Destructive delete_clip_markers_by_color Delete all markers of a specific color on a clip. Args: clip_id: Unique ID of

All 369 DaVinci Resolve MCP tools →

Execute tools on other servers

Frida Game Hacking MCP remove_breakpoint Procmon request_elevation WireMCP capture_packets Pentest Ai run_probe

Go deeper

High-risk tools in DaVinci Resolve MCP → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

What does the fuse_plugin tool do? +

Author and install Fusion Fuse plugins (.fuse files). Fuses are Lua plugins (or GLSL view-LUT shaders) that Fusion loads at startup. A NEW Fuse requires a Resolve restart to register; existing Fuses can be edited and reloaded from the Inspector's Edit/Reload buttons without restart. The MCP cannot trigger reload — that's a UI-only action. Actions: path() -> {fuses_dir} list() -> {fuses} — Fuses with the @mcp-fuse marker comment. list(all=true) -> {fuses} — All .fuse files in the directory. install(name, source, overwrite?) -> {success, path} — name: [A-Za-z_][A-Za-z0-9_]* — source: full Fuse source (Lua, or Lua+GLSL for view LUTs) — overwrite: bool (default false) remove(name) -> {success} read(name) -> {source} validate(source, type?) -> {valid, errors, checker} — type: 'lua' (default) | 'glsl' template(kind, name, options?) -> {source, kind, name} — Returns generated source. Pass it to install() to write to disk. — kind: one of the keys returned by list_templates(). See docs/authoring/fuse-dctl-authoring.md for the per-kind option spec. list_templates() -> {kinds}. It is categorised as a Execute tool in the DaVinci Resolve MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on fuse_plugin? +

Register the DaVinci Resolve MCP server in PolicyLayer and add a rule for fuse_plugin: 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 fuse_plugin? +

fuse_plugin is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit fuse_plugin? +

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

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

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

// WHAT FUSE_PLUGIN ON DAVINCI RESOLVE MCP DOES

// THE RISK

// HOW TO CONTROL FUSE_PLUGIN

// EXPLORE