# export_sequence

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

Agent View of the PolicyLayer registry record for `export_sequence`. HTML page: https://policylayer.com/tools/adobe-premiere-pro-mcp/export-sequence

## Facts

- Tool: `export_sequence`
- Server: Adobe Premiere Pro (`adobe-premiere-pro-mcp`) — https://policylayer.com/tools/adobe-premiere-pro-mcp.md
- Install: `npx -y adobe-premiere-pro-mcp`
- Homepage: https://www.npmjs.com/package/adobe-premiere-pro-mcp
- Risk category: Execute (High risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 10 (2 required)
- Recommended policy verdict: Rate-limited

## Parameters

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

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "export_sequence",
    "arguments": {
      "outputPath": "<outputPath>",
      "sequenceId": "<sequenceId>"
    }
  }
}
```

## 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 own definition: "Renders and exports a sequence to a video file. This is for creating the final video."

Risk signals: High parameter count (10 properties)

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Adobe Premiere Pro:

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

## Other tools on Adobe Premiere Pro (282)

- `clear_item_in_out` — Destructive — https://policylayer.com/tools/adobe-premiere-pro-mcp/clear-item-in-out.md
- `clear_sequence_in_out` — Destructive — https://policylayer.com/tools/adobe-premiere-pro-mcp/clear-sequence-in-out.md
- `delete_bin` — Destructive — https://policylayer.com/tools/adobe-premiere-pro-mcp/delete-bin.md
- `delete_marker` — Destructive — https://policylayer.com/tools/adobe-premiere-pro-mcp/delete-marker.md
- `delete_multiple_project_items` — Destructive — https://policylayer.com/tools/adobe-premiere-pro-mcp/delete-multiple-project-items.md
- `delete_preview_files` — Destructive — https://policylayer.com/tools/adobe-premiere-pro-mcp/delete-preview-files.md
- `delete_project_item` — Destructive — https://policylayer.com/tools/adobe-premiere-pro-mcp/delete-project-item.md
- `delete_sequence` — Destructive — https://policylayer.com/tools/adobe-premiere-pro-mcp/delete-sequence.md
- `delete_track` — Destructive — https://policylayer.com/tools/adobe-premiere-pro-mcp/delete-track.md
- `remove_all_effects` — Destructive — https://policylayer.com/tools/adobe-premiere-pro-mcp/remove-all-effects.md
- `remove_effect` — Destructive — https://policylayer.com/tools/adobe-premiere-pro-mcp/remove-effect.md
- `remove_effect_by_name` — Destructive — https://policylayer.com/tools/adobe-premiere-pro-mcp/remove-effect-by-name.md
- `remove_from_timeline` — Destructive — https://policylayer.com/tools/adobe-premiere-pro-mcp/remove-from-timeline.md
- `remove_keyframe` — Destructive — https://policylayer.com/tools/adobe-premiere-pro-mcp/remove-keyframe.md
- `remove_keyframe_range` — Destructive — https://policylayer.com/tools/adobe-premiere-pro-mcp/remove-keyframe-range.md
- `remove_selected_clips` — Destructive — https://policylayer.com/tools/adobe-premiere-pro-mcp/remove-selected-clips.md
- `ripple_delete` — Destructive — https://policylayer.com/tools/adobe-premiere-pro-mcp/ripple-delete.md
- `add_to_render_queue` — Execute — https://policylayer.com/tools/adobe-premiere-pro-mcp/add-to-render-queue.md
- `auto_reframe_sequence` — Execute — https://policylayer.com/tools/adobe-premiere-pro-mcp/auto-reframe-sequence.md
- `build_brand_spot_from_mogrt_and_assets` — Execute — https://policylayer.com/tools/adobe-premiere-pro-mcp/build-brand-spot-from-mogrt-and-assets.md
- `build_motion_graphics_demo` — Execute — https://policylayer.com/tools/adobe-premiere-pro-mcp/build-motion-graphics-demo.md
- `execute_extendscript` — Execute — https://policylayer.com/tools/adobe-premiere-pro-mcp/execute-extendscript.md
- `open_project` — Execute — https://policylayer.com/tools/adobe-premiere-pro-mcp/open-project.md
- `set_playhead_position` — Execute — https://policylayer.com/tools/adobe-premiere-pro-mcp/set-playhead-position.md
- `start_batch_encode` — Execute — https://policylayer.com/tools/adobe-premiere-pro-mcp/start-batch-encode.md
- `stop_playback` — Execute — https://policylayer.com/tools/adobe-premiere-pro-mcp/stop-playback.md
- `undo` — Execute — https://policylayer.com/tools/adobe-premiere-pro-mcp/undo.md
- `consolidate_and_transfer` — Financial — https://policylayer.com/tools/adobe-premiere-pro-mcp/consolidate-and-transfer.md
- `check_offline_media` — Read — https://policylayer.com/tools/adobe-premiere-pro-mcp/check-offline-media.md
- `detect_silence` — Read — https://policylayer.com/tools/adobe-premiere-pro-mcp/detect-silence.md
- …and 252 more: https://policylayer.com/tools/adobe-premiere-pro-mcp.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=adobe-premiere-pro-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/adobe-premiere-pro-mcp