// SCAN REPORT

REAPER MCP Server

45 tools. 43 can modify or destroy data without limits.

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

Last updated: 11 Jun 2026

43 can modify or destroy data

2 read-only

45 tools total

Community server · catalogue entry verified 11/06/2026

How to control REAPER MCP Server ↓

TOOL MAP

Read (2) Write / Execute (40) Destructive / Financial (3)

MOST DANGEROUS TOOLS

Critical Risk

Destructive · High dsl_track_delete_all Deleting all tracks in a REAPER project irreversibly removes audio data and project structure that cannot be easily recovered. Destructive · Medium dsl_reset_context The tool resets context and clears references, which is likely irreversible — once the context is wiped, prior session state and references cannot be recovered. Destructive · High dsl_track_delete The 'delete' verb combined with 'track' context places this firmly in the Destructive category. Execute · Low dsl_play This tool triggers an external operation (audio playback) whose effects depend on the current state of the loaded project and playback settings.

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

HOW TO CONTROL REAPER MCP SERVER

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

Deny destructive operations

{
  "dsl_reset_context": {
    "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

{
  "dsl_add_effect": {
    "limits": [
      {
        "counter": "dsl_add_effect_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "dsl_get_tempo_info": {
    "limits": [
      {
        "counter": "dsl_get_tempo_info_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 REAPER 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 REAPER →

Free to start. No card required.

ALL 45 REAPER MCP SERVER TOOLS

DESTRUCTIVE 3 tools

Destructive dsl_reset_context Start fresh with a clean slate. Use when users want to begin again or clear previous references. Destructive dsl_track_delete dsl_track_delete Destructive dsl_track_delete_all dsl_track_delete_all

EXECUTE 5 tools

Execute dsl_play Start playing your music. Use for any variation of play, start, go, listen, or hear. Execute dsl_record Start recording. Use for 'record', 'start recording', 'rec'. Execute dsl_stop Stop the music. Use for stop, pause, halt, wait, or cease playback. Execute dsl_quantize dsl_quantize Execute dsl_render dsl_render

WRITE 35 tools

Write dsl_add_effect Add an effect to a track. Use for 'add reverb to vocals', 'put compression on drums', Write dsl_adjust_effect Adjust effect parameters. Use for 'make reverb wetter', 'increase compression ratio', Write dsl_automate Create automation. Use for 'automate volume', 'fade in over 4 bars', 'pan left to right', Write dsl_automate_section Apply automation to a section. Use for 'increase energy in chorus', 'duck everything in verse', Write dsl_continue dsl_continue Write dsl_create_bus Create a bus and route tracks to it. Use for 'create drum bus', 'make vocal bus with compression', Write dsl_create_send Create a send between tracks. Use for 'send vocals to reverb', 'route drums to bus', Write dsl_effect_bypass Bypass or enable effects. Use for 'bypass reverb', 'turn off compression', Write dsl_enhance dsl_enhance Write dsl_fade dsl_fade Write dsl_generate dsl_generate Write dsl_go_to dsl_go_to Write dsl_group_tracks dsl_group_tracks Write dsl_loop_create dsl_loop_create Write dsl_marker dsl_marker Write dsl_midi_insert dsl_midi_insert Write dsl_normalize dsl_normalize Write dsl_region dsl_region Write dsl_reverse Reverse audio. Use for 'reverse', 'play backwards', 'flip audio'. Write dsl_save Save the project. Use for 'save', 'save project', 'save as'. Write dsl_select dsl_select Write dsl_send dsl_send Write dsl_set_tempo dsl_set_tempo Write dsl_split dsl_split Write dsl_time_select dsl_time_select Write dsl_track_arm dsl_track_arm Write dsl_track_color dsl_track_color Write dsl_track_create dsl_track_create Write dsl_track_duplicate dsl_track_duplicate Write dsl_track_mute dsl_track_mute Write dsl_track_pan dsl_track_pan Write dsl_track_rename dsl_track_rename Write dsl_track_solo dsl_track_solo Write dsl_track_volume dsl_track_volume Write dsl_undo Undo the last action. Use for 'undo', 'undo that', 'go back', 'revert'.

READ 2 tools

Read dsl_get_tempo_info Check current speed and time signature. Use when users ask about tempo, BPM, or timing. Read dsl_list_tracks Show what's in your project. Use when users ask what tracks exist or want an overview.

RELATED SERVERS

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

FAQ

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

Yes. The REAPER MCP Server server exposes 3 destructive tools including dsl_reset_context, dsl_track_delete, dsl_track_delete_all. 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 REAPER MCP Server? +

The REAPER MCP Server server has 35 write tools including dsl_add_effect, dsl_adjust_effect, dsl_automate. 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 REAPER MCP Server.

How many tools does the REAPER MCP Server MCP server expose? +

45 tools across 4 categories: Destructive, Execute, Read, Write. 2 are read-only. 43 can modify, create, or delete data.

How do I enforce a policy on REAPER MCP Server? +

Register the REAPER 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 REAPER MCP Server tool call.

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

ENFORCE POLICY ON REAPER →

Free to start. No card required.

45 REAPER MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

REAPER MCP Server

// TOOL MAP

// MOST DANGEROUS TOOLS

// HOW TO CONTROL REAPER MCP SERVER

// ALL 45 REAPER MCP SERVER TOOLS

// RELATED SERVERS

// FAQ