Critical Risk →

delete_midi_note

Delete a MIDI note from an item.

How to control delete_midi_note ↓

What delete_midi_note does on Reaper

AI agents call delete_midi_note to permanently remove resources in Reaper — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why delete_midi_note needs a policy

This tool permanently removes MIDI note data from a music production project. Deletion is irreversible—once a MIDI note is deleted, it cannot be recovered through the tool's normal operation.

From the tool's definition Tool name is 'delete_midi_note' and description states 'Delete a MIDI note from an item.' The verb 'Delete' indicates irreversible removal of data.

Documented attack patterns abuse exactly the kind of access delete_midi_note gives an agent:

How to control delete_midi_note

PolicyLayer is an MCP gateway — it sits between your AI agents and Reaper, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_midi_note:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_midi_note"
  ]
}

delete_midi_note disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register Reaper — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about delete_midi_note

What does the delete_midi_note tool do? +

Delete a MIDI note from an item. It is categorised as a Destructive tool in the Reaper MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on delete_midi_note? +

Register the Reaper MCP server in PolicyLayer and add a rule for delete_midi_note: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Reaper. Nothing to install.

What risk level is delete_midi_note? +

delete_midi_note is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_midi_note? +

Yes. Add a rate_limit block to the delete_midi_note rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.

How do I block delete_midi_note completely? +

Set action: deny in the PolicyLayer policy for delete_midi_note. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.

What MCP server provides delete_midi_note? +

delete_midi_note is provided by the Reaper MCP server (twelvetake-studios/reaper-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Reaper tool call.

Start from Reaper, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

158 Reaper tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.