AI agents call delete_item to permanently remove resources in Reaper Reapy — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The 'delete_item' operation irreversibly removes data (audio or MIDI items) from a REAPER project. This cannot be undone programmatically via MCP and represents a destructive action with a blast radius of potential data loss if an AI agent misuses arguments or makes incorrect decisions about what to delete.
From the tool's definition Tool name 'delete_item' indicates irreversible deletion. Context shows this is part of a REAPER DAW control suite where items represent audio/MIDI data segments.
Documented attack patterns abuse exactly the kind of access delete_item gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Reaper Reapy, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_item:
{
"version": "1",
"default": "deny",
"hide": [
"delete_item"
]
}delete_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_item. It is categorised as a Destructive tool in the Reaper Reapy MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Reaper Reapy MCP server in PolicyLayer and add a rule for delete_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 Reapy. Nothing to install.
delete_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 delete_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 delete_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.
delete_item is provided by the Reaper Reapy MCP server (wegitor/reaper-reapy-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 47 Reaper Reapy tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
47 Reaper Reapy tools catalogued and risk-classified — across an index of 42,500+ MCP servers.