Import content into the current timeline from a file. Args: file_path: Path to the file to import (AAF, EDL, XML, etc.). import_options: Optional dict of import options.
AI agents use timeline_import_into 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 creates or modifies data (timeline content) in a reversible manner by importing files. This fits the Write category rather than Read (has side effects) or Execute (not arbitrary code execution, though it does trigger an operation). Severity is high because importing large or malicious files could corrupt a project or introduce unexpected timeline changes, affecting production workflows.
From the tool's definition Tool description states 'Import content into the current timeline from a file' with support for AAF, EDL, XML formats. This creates/modifies the timeline by importing external content, which is a write operation with side effects on the active project.
Documented attack patterns abuse exactly the kind of access timeline_import_into 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 timeline_import_into:
{
"version": "1",
"default": "deny",
"tools": {
"timeline_import_into": {
"limits": [
{
"counter": "timeline_import_into_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}timeline_import_into 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 content into the current timeline from a file. Args: file_path: Path to the file to import (AAF, EDL, XML, etc.). 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 timeline_import_into: 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.
timeline_import_into 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 timeline_import_into 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 timeline_import_into. 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.
timeline_import_into 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.