import_sequences_from_project
Imports sequences from another Premiere Pro project file.
This record as markdown: /tools/adobe-premiere-pro-mcp/import-sequences-from-project.md
What import_sequences_from_project does on Adobe Premiere Pro
AI agents use import_sequences_from_project to create or update resources in Adobe Premiere Pro, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Adobe Premiere Pro environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
projectPath | string | Yes | The absolute path to the source .prproj file |
sequenceIds | array | Yes | Array of sequence IDs to import from the source project |
Parameters from the server's own tool schema.
Why import_sequences_from_project is rated Medium
The import action creates new sequences within the current project, which is a reversible modification of project data. This is a Write operation rather than Read (it modifies state), Execute (it doesn't run arbitrary code), or Destructive (imports are reversible and don't delete existing content).
From the tool's definition Tool description states it 'Imports sequences from another Premiere Pro project file' - this creates or adds content to the current project, modifying its structure and composition.
Attacks that exploit this kind of access
The rule that runs import_sequences_from_project safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Adobe Premiere Pro, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For import_sequences_from_project, this is the rule to start with:
import_sequences_from_project 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 Adobe Premiere Pro, apply this rule, and every import_sequences_from_project call is checked against it from then on.
Questions about import_sequences_from_project
Imports sequences from another Premiere Pro project file. It is categorised as a Write tool in the Adobe Premiere Pro MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
import_sequences_from_project accepts 2 parameters: projectPath, sequenceIds. Required: projectPath, sequenceIds. The full parameter table on this page comes from the server's own tool schema.
Register the Adobe Premiere Pro MCP server in PolicyLayer and add a rule for import_sequences_from_project: 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 Adobe Premiere Pro. Nothing to install.
import_sequences_from_project 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_sequences_from_project 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_sequences_from_project. 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_sequences_from_project is provided by the Adobe Premiere Pro MCP server (adobe-premiere-pro-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Adobe Premiere Pro, and thousands of servers like it.
This server
Across the catalogue