timeline_import_into
Import content into the current timeline from a file.
This record as markdown: /tools/samuelgursky-davinci-resolve-mcp/timeline-import-into.md
What timeline_import_into does on DaVinci Resolve MCP
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.
Why timeline_import_into is rated Medium
The tool adds or incorporates external content into an active project timeline, which constitutes data creation and modification. While reversible and not destructive, it materially alters the project state.
From the tool's definition Tool description: 'Import content into the current timeline from a file.' The action of importing creates new data structures in the timeline (clips, sequences, effects) that modify the current project state.
Attacks that exploit this kind of access
The rule that runs timeline_import_into safely
PolicyLayer is an MCP gateway: it sits between your AI agents and DaVinci Resolve MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For timeline_import_into, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect DaVinci Resolve MCP, apply this rule, and every timeline_import_into call is checked against it from then on.
Questions about timeline_import_into
Import content into the current timeline from a file. 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.
More on DaVinci Resolve, and thousands of servers like it.
This server
Across the catalogue