// SCAN REPORT

Scythe MCP REAPER

24 tools. 23 can modify or destroy data without limits.

23 write tools that can modify data. Rate limits recommended.

Last updated: 4 Jul 2026

23 can modify or destroy data

1 read-only

24 tools total

Community server · catalogue entry verified 04/07/2026

How to control Scythe MCP REAPER ↓

TOOL MAP

What Scythe MCP REAPER exposes to your agents

Read (1) Write / Execute (23) Destructive / Financial (0)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous Scythe MCP REAPER tools

Execute · Critical execute_lua execute_lua directly runs code with effects determined entirely by the argument (the Lua script content). Execute · Medium play The tool executes a command (start playback) that has observable effects on an external system (the DAW). Execute · High record The 'record' tool executes a state-changing action on REAPER (starting audio/MIDI recording). Execute · Low stop While stopping playback is a benign action with no data destruction or financial impact, it is fundamentally an Execute operation—it triggers a state change in an external system (REAPER) based on the tool invocation.

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

POLICY

How to control Scythe MCP REAPER

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

Rate limit write operations

{
  "add_bass_track": {
    "limits": [
      {
        "counter": "add_bass_track_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "get_session_info": {
    "limits": [
      {
        "counter": "get_session_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 Scythe MCP REAPER — 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 SCYTHE MCP REAPER →

Instant setup, no code required.

FULL CATALOGUE

All 24 Scythe MCP REAPER tools

EXECUTE 6 tools

Execute execute_lua execute_lua Execute goto_position Move cursor to a specific position. Execute play Start playback. Execute record Start recording. Execute stop Stop playback. Execute trigger_action trigger_action

WRITE 17 tools

Write add_bass_track Generate and add a bass track provided a chord progression. Write add_drum_track Generate and add a drum track. Write add_melody_track Generate and add a melody track. Write add_notes add_notes Write arm_track Arm or disarm a track for recording. Write create_midi_item Create a MIDI item on a track. Write create_song_sketch Generate a full song sketch (Drums, Bass, Harmony, Melody). Write create_track Create a new track. Write generate_bass_json Generate bassline data (JSON) from chord progression. Write generate_drums_json Generate drum pattern data (JSON) to be used with add_notes. Write generate_melody_json Generate melody data (JSON). Write mute_track Mute or unmute a track. Write select_track Select a track. Write set_tempo Set the project tempo in BPM. Write set_track_pan Set track pan position. Write set_track_volume Set track volume. Write solo_track Solo or unsolo a track.

READ 1 tools

Read get_session_info Get information about REAPER. Note: OSC is primarily for sending commands.

EXPLORE

Related servers

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

FAQ

Questions about Scythe MCP REAPER

How do I prevent bulk modifications through Scythe MCP REAPER? +

The Scythe MCP REAPER server has 17 write tools including add_bass_track, add_drum_track, add_melody_track. 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 Scythe MCP REAPER.

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

24 tools across 3 categories: Execute, Read, Write. 1 are read-only. 23 can modify, create, or delete data.

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

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

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

ENFORCE POLICY ON SCYTHE MCP REAPER →

Instant setup, no code required.

24 Scythe MCP REAPER tools catalogued and risk-classified — across an index of 43,000+ MCP servers.