// SCAN REPORT

Pro Tools MCP Server

36 tools. 22 can modify or destroy data without limits.

4 destructive tools with no built-in limits. Policy required.

Last updated: 12 Jun 2026

22 can modify or destroy data

14 read-only

36 tools total

Community server · catalogue entry verified 12/06/2026

How to control Pro Tools MCP Server ↓

TOOL MAP

What Pro Tools MCP Server exposes to your agents

Read (14) Write / Execute (18) Destructive / Financial (4)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Pro Tools MCP Server tools

Destructive · High clear This tool irreversibly deletes audio content from a Pro Tools session. Destructive · High delete_all_markers This tool performs a bulk deletion operation that cannot be undone. Destructive · High delete_marker This tool permanently removes markers from a Pro Tools audio editing session. Destructive · High cut A cut operation removes content from the timeline.

22 of Pro Tools MCP Server's 36 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Pro Tools MCP Server

PolicyLayer is an MCP gateway — it sits between your AI agents and Pro Tools MCP Server, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations

{
  "clear": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "paste": {
    "limits": [
      {
        "counter": "paste_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "analyze_audio": {
    "limits": [
      {
        "counter": "analyze_audio_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Pro Tools MCP Server — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON PRO TOOLS →

Free to start. No card required.

FULL CATALOGUE

All 36 Pro Tools MCP Server tools

DESTRUCTIVE 4 tools

Destructive clear Clear (delete) the selected content on selected tracks within the timeline selection without copying to clipbo Destructive delete_all_markers Delete all markers/memory locations in the session Destructive delete_marker Delete one or more markers by their numbers Destructive cut Cut the selected content on selected tracks within the timeline selection. Use select_tracks and set_timeline_

EXECUTE 6 tools

Execute play Start playback in Pro Tools Execute ptsl_command Execute a raw PTSL command with custom parameters. Use this for advanced operations not covered by high-level Execute record Start recording in Pro Tools Execute stop Stop playback/recording in Pro Tools Execute toggle_play Toggle between play and stop Execute select_clip_on_timeline Highlights a specific range on the Pro Tools timeline. Use the track_name, start_time, and end_time

WRITE 12 tools

Write paste Paste previously copied/cut content at the current timeline position on selected tracks. Write redo Redo the last undone operation Write undo Undo the last editing operation Write copy Copy the selected content on selected tracks within the timeline selection. Use select_tracks and set_timeline Write create_marker Create a new marker/memory location at a specific time Write edit_marker Edit an existing marker/memory location Write save_session Save the current Pro Tools session Write select_tracks Select tracks by name in Pro Tools Write set_playback_mode Set the playback mode (normal, loop, or dynamic transport) Write set_timeline_selection Set the timeline selection (in/out points) for editing operations. Times can be in samples, timecode, or other Write set_track_mute Mute or unmute tracks in Pro Tools Write set_track_solo Solo or unsolo tracks in Pro Tools

READ 14 tools

Read analyze_audio Analyze a specific audio region from Pro Tools. Supports visual analysis (waveform/spectrogram), Read get_clip_list Get the clip library - all imported audio files available in the session. Read get_markers Get all memory locations/markers in the session Read get_session_info Get information about the current Pro Tools session (name, path, sample rate) Read get_session_length Get the session length (duration from start to the end of the last content) Read get_session_overview Get comprehensive overview of the Pro Tools session including format details, tracks, Read get_timeline_clips Get clips CURRENTLY PLACED ON THE TIMELINE with their timeline positions and durations. Read get_timeline_selection Get the current timeline selection (in/out points) Read get_timeline_tracks Get a list of all tracks from the locally cached timeline index. Read get_track_list Get a list of all tracks in the current Pro Tools session with their properties Read refresh_pro_tools_index Synchronizes the local cache with the Pro Tools timeline. Read sample_ptsl_responses Sample actual JSON responses from various PTSL commands to verify response formatting. Logs output to server c Read search_timeline Fast search of the locally cached timeline index. Queries audio clip names and track names. Read select_marker Jump to a specific marker by its number

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about Pro Tools MCP Server

Can an AI agent delete data through the Pro Tools MCP Server MCP server? +

Yes. The Pro Tools MCP Server server exposes 4 destructive tools including clear, delete_all_markers, delete_marker. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Pro Tools MCP Server? +

The Pro Tools MCP Server server has 12 write tools including paste, redo, undo. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Pro Tools MCP Server.

How many tools does the Pro Tools MCP Server MCP server expose? +

36 tools across 4 categories: Destructive, Execute, Read, Write. 14 are read-only. 22 can modify, create, or delete data.

How do I enforce a policy on Pro Tools MCP Server? +

Register the Pro Tools MCP Server MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Pro Tools MCP Server tool call.

Deterministic rules across all 36 Pro Tools MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON PRO TOOLS →

Free to start. No card required.

36 Pro Tools MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.