AI agents call clear_midi_item 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.
This tool irreversibly removes all MIDI note data from a REAPER track item. While the damage is scoped to a single item rather than the entire project, the loss is unrecoverable without undo (which an AI agent may not trigger). In a music production context, hours of compositional work could be lost. This meets the Destructive category definition: irreversibly deletes data that cannot be undone by the tool itself.
From the tool's definition 'Delete all MIDI notes from an item' - uses the word 'Delete' and describes permanent removal of MIDI note data without reversibility mechanism.
Documented attack patterns abuse exactly the kind of access clear_midi_item gives an agent:
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 clear_midi_item:
{
"version": "1",
"default": "deny",
"hide": [
"clear_midi_item"
]
}clear_midi_item disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Delete all MIDI notes 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.
Register the Reaper MCP server in PolicyLayer and add a rule for clear_midi_item: 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.
clear_midi_item is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the clear_midi_item 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.
Set action: deny in the PolicyLayer policy for clear_midi_item. 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.
clear_midi_item 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.
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.