Critical-risk tools in ReaperMCP
12 of the 138 tools in ReaperMCP are classified as critical risk. This page profiles those tools specifically, with recommended policy actions and the attack patterns that target them.
Every operation listed below is an action PolicyLayer recommends controlling at the transport layer. Open any tool to see the full profile, risk score, and YAML policy snippet.
Tools at critical risk
-
envelope_clear_rangeDestructiveenvelope_clear_range
-
fx_removeDestructiveRemove FX from track chain.
-
item_deleteDestructiveDelete an item.
-
marker_deleteDestructiveDelete marker/region.
-
midi_delete_all_notesDestructiveClear all notes from a MIDI item.
-
midi_delete_ccDestructiveDelete a CC event.
-
midi_delete_noteDestructiveDelete a note.
-
tempo_clear_allDestructiveDelete every tempo/time-sig marker — resets the project to its base tempo.
-
tempo_delete_markerDestructiveDelete a tempo/time-sig marker by its index (from `tempo_list_markers`).
-
track_deleteDestructiveDelete a track.
-
track_template_deleteDestructiveDelete a saved track template.
-
item_take_delete_activeDestructiveDelete the currently active take from an item.
Attacks that target this class
Critical-risk tools in any server share these documented attack patterns. Each links to the full case and the defensive policy.