export_sequence

Renders and exports a sequence to a video file. This is for creating the final video.

SERVERAdobe Premiere Pro SOURCEadobe-premiere-pro-mcp

High RISK CLASS

Category Execute

Parameters 102 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/adobe-premiere-pro-mcp/export-sequence.md

WHAT IT DOES

What export_sequence does on Adobe Premiere Pro

AI agents invoke export_sequence to trigger actions in Adobe Premiere Pro. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

Parameter	Type	Required	Description
`format`	string	—	Deprecated hint only; the .epr preset controls codec/container.
`quality`	string	—	Deprecated hint only; the .epr preset controls quality.
`outputPath`	string	Yes	The absolute path where the final video file will be saved
`presetName`	string	—	Exact user preset display name or filename stem. Must resolve to exactly one discovered .epr preset.
`presetPath`	string	—	Absolute path to an export preset file (.epr). Required unless presetName uniquely resolves through get_encoder_presets.
`resolution`	string	—	Deprecated hint only; the .epr preset controls resolution.
`sequenceId`	string	Yes	The ID of the sequence to export
`sourceRange`	string	—	Export source range. Defaults to entire. Requested ranges are never silently substituted.
`allowOverwrite`	boolean	—	Allow writing to an existing output file. Defaults to false.
`removeOnCompletion`	boolean	—	Pass AME removeOnCompletion. Defaults to true to preserve existing queue behavior.

Parameters from the server's own tool schema.

RISK

Why export_sequence is rated High

This tool triggers an external rendering/export operation in Adobe Premiere Pro, producing a video file on disk. It executes a long-running process with real-world side effects (file creation, resource consumption). While it creates a new file (Write-like), the dominant characteristic is triggering an external operation whose effects depend on the sequence content and export settings — classifying it as Execute.

From the tool's definition Renders and exports a sequence to a video file. This is for creating the final video.

Risk signalsHigh parameter count (10 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs export_sequence 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_sequence, this is the rule to start with:

export_sequence Rate-limited

export_sequence stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "export_sequence": {
      "limits": [
        {
          "counter": "export_sequence_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Adobe Premiere Pro, apply this rule, and every export_sequence call is checked against it from then on.

FAQ

Questions about export_sequence

What does the export_sequence tool do? +

Renders and exports a sequence to a video file. This is for creating the final video. It is categorised as a Execute tool in the Adobe Premiere Pro MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

What parameters does export_sequence accept? +

export_sequence accepts 10 parameters: format, quality, outputPath, presetName, presetPath, resolution, sequenceId, sourceRange, allowOverwrite, removeOnCompletion. Required: outputPath, sequenceId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on export_sequence? +

Register the Adobe Premiere Pro MCP server in PolicyLayer and add a rule for export_sequence: 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.

What risk level is export_sequence? +

export_sequence is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit export_sequence? +

Yes. Add a rate_limit block to the export_sequence 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.

How do I block export_sequence completely? +

Set action: deny in the PolicyLayer policy for export_sequence. 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.

What MCP server provides export_sequence? +

export_sequence 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.

KEEP EXPLORING

More on Adobe Premiere Pro, and thousands of servers like it.

This server

All 283 Adobe Premiere Pro tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →