Get a Fusion composition from a timeline item by name. Args: comp_name: Name of the Fusion composition to retrieve. track_type: Track type ('video', 'audio', 'subtitle'). track_index: Track index (1-based). item_index: Item index on the track (0-based).
AI agents call get_fusion_comp_by_name to retrieve information from DaVinci Resolve MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries existing Fusion composition data from a timeline without creating, modifying, deleting, or executing any external operations. It is a straightforward read operation that returns composition metadata or references. The blast radius of misuse is minimal — an AI agent querying the wrong composition name would at worst retrieve incorrect data, with no irreversible consequences.
From the tool's definition Tool description states 'Get a Fusion composition from a timeline item by name' — the verb 'Get' and the retrieval-focused parameters (comp_name, track_type, track_index, item_index) indicate data querying with no modification or side effects.
Documented attack patterns abuse exactly the kind of access get_fusion_comp_by_name 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 get_fusion_comp_by_name:
{
"version": "1",
"default": "deny",
"tools": {
"get_fusion_comp_by_name": {}
}
}get_fusion_comp_by_name is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get a Fusion composition from a timeline item by name. Args: comp_name: Name of the Fusion composition to retrieve. track_type: Track type ('video', 'audio', 'subtitle'). track_index: Track index (1-based). item_index: Item index on the track (0-based). It is categorised as a Read tool in the DaVinci Resolve MCP MCP Server, which means it retrieves data without modifying state.
Register the DaVinci Resolve MCP server in PolicyLayer and add a rule for get_fusion_comp_by_name: 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.
get_fusion_comp_by_name is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_fusion_comp_by_name 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 get_fusion_comp_by_name. 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.
get_fusion_comp_by_name 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.