AI agents call delete_selected_items 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 permanently removes audio items or tracks from a REAPER project without the ability to undo via the tool itself (undo depends on REAPER's state management, not tool design). In a music production context, deleting selected items can result in loss of hours of work. An AI agent misusing this tool could destroy critical parts of a user's project.
From the tool's definition The tool is named 'delete_selected_items' and the description states 'Delete all selected items,' using the irreversible action verb 'delete.'
Documented attack patterns abuse exactly the kind of access delete_selected_items 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 delete_selected_items:
{
"version": "1",
"default": "deny",
"hide": [
"delete_selected_items"
]
}delete_selected_items 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 selected items. 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 delete_selected_items: 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.
delete_selected_items 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 delete_selected_items 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 delete_selected_items. 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.
delete_selected_items 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.