AI agents call delete_region 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/MIDI regions from a REAPER project. Regions represent edited content that cannot be recovered after deletion. While the blast radius is limited to the current project (not system-wide), accidental or malicious deletion of regions during music production is a significant loss that cannot be undone programmatically.
From the tool's definition Tool name is 'delete_region' and description states 'Delete a region by index.' The verb 'delete' combined with the action of removing a region from a REAPER project indicates irreversible data destruction.
Documented attack patterns abuse exactly the kind of access delete_region 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_region:
{
"version": "1",
"default": "deny",
"hide": [
"delete_region"
]
}delete_region 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 a region by index. 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_region: 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_region 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_region 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_region. 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_region 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.