Import a timeline from a file (AAF, EDL, XML, FCPXML, DRT, ADL, OTIO). Args: file_path: Absolute path to the timeline file. import_options: Optional dict of import options.
AI agents use import_timeline_from_file 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.
This is a Write operation because it creates or modifies project data (timelines) within DaVinci Resolve. It is not Destructive because the operation is reversible (the timeline can be removed or the project can be closed without saving). It is not Execute because it does not run arbitrary code or shell commands—it performs a structured import operation.
From the tool's definition The tool 'import_timeline_from_file' imports a timeline from a file into DaVinci Resolve, which modifies the project state by adding or creating timeline data.
Documented attack patterns abuse exactly the kind of access import_timeline_from_file 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 import_timeline_from_file:
{
"version": "1",
"default": "deny",
"tools": {
"import_timeline_from_file": {
"limits": [
{
"counter": "import_timeline_from_file_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}import_timeline_from_file 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.
Import a timeline from a file (AAF, EDL, XML, FCPXML, DRT, ADL, OTIO). Args: file_path: Absolute path to the timeline file. import_options: Optional dict of import options. 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 import_timeline_from_file: 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.
import_timeline_from_file 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 import_timeline_from_file 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 import_timeline_from_file. 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.
import_timeline_from_file 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.