import_fcp_xml
Imports a Final Cut Pro 7 XML (XMEML) file into the current project. Premiere creates a new sequence with the cuts/clips defined in the XML. The import requests Premiere UI suppression, but malformed or unsupported XML can still be rejected by Premiere. Use legacy FCP7 XML, not modern FCPXML 1.x ...
This record as markdown: /tools/adobe-premiere-pro-mcp/import-fcp-xml.md
What import_fcp_xml does on Adobe Premiere Pro
AI agents use import_fcp_xml 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 |
|---|---|---|---|
filePath | string | Yes | The absolute path to the FCP7 XML file (.xml extension typical) |
Parameters from the server's own tool schema.
Why import_fcp_xml is rated Medium
Creates new project sequences and modifies timeline state reversibly; high confidence due to explicit creation semantics and blast radius if importing malicious or corrupted XML into workflows.
From the tool's definition Imports FCP7 XML file, creates new sequence with clips/cuts
Risk signalsAccepts file system path (filePath)
Attacks that exploit this kind of access
The rule that runs import_fcp_xml 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_fcp_xml, this is the rule to start with:
import_fcp_xml 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_fcp_xml call is checked against it from then on.
Questions about import_fcp_xml
Imports a Final Cut Pro 7 XML (XMEML) file into the current project. Premiere creates a new sequence with the cuts/clips defined in the XML. The import requests Premiere UI suppression, but malformed or unsupported XML can still be rejected by Premiere. Use legacy FCP7 XML, not modern FCPXML 1.x from Final Cut Pro X. 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_fcp_xml accepts 1 parameter: filePath. Required: filePath. 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_fcp_xml: 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_fcp_xml 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_fcp_xml 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_fcp_xml. 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_fcp_xml 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