export_aaf
Exports a sequence as an AAF file for interchange with other editing/audio applications.
This record as markdown: /tools/adobe-premiere-pro-mcp/export-aaf.md
What export_aaf does on Adobe Premiere Pro
AI agents use export_aaf 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 |
|---|---|---|---|
outputPath | string | Yes | The absolute file path for the exported AAF file |
sampleRate | number | — | Audio sample rate (default: 48000) |
sequenceId | string | Yes | The ID of the sequence to export |
mixDownVideo | boolean | — | Whether to mix down video (default: true) |
bitsPerSample | number | — | Audio bits per sample (default: 16) |
explodeToMono | boolean | — | Whether to explode audio to mono (default: false) |
Parameters from the server's own tool schema.
Why export_aaf is rated Medium
This tool creates/exports data (AAF file) in a reversible manner. While it generates output that could overwrite an existing file, the primary function is creating/exporting data for interchange purposes, not deletion or destruction. The severity is medium because a poorly-targeted export could overwrite user files unintentionally, but the action is reversible (exported files can be deleted or re-exported).
From the tool's definition Tool name 'export_aaf' and description 'Exports a sequence as an AAF file' indicate file creation/output generation. AAF (Advanced Authoring Format) is an interchange format that results in a new file being written to disk.
Attacks that exploit this kind of access
The rule that runs export_aaf 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 export_aaf, this is the rule to start with:
export_aaf 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 export_aaf call is checked against it from then on.
Questions about export_aaf
Exports a sequence as an AAF file for interchange with other editing/audio applications. 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.
export_aaf accepts 6 parameters: outputPath, sampleRate, sequenceId, mixDownVideo, bitsPerSample, explodeToMono. Required: outputPath, sequenceId. 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 export_aaf: 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.
export_aaf 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 export_aaf 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 export_aaf. 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.
export_aaf 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