AI agents call track_delete to permanently remove resources in ReaperMCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting a track in a REAPER project irreversibly removes audio data, automation, effects, and arrangement information that cannot be recovered unless the project is reverted or undo is available within REAPER itself. In the context of an AI agent autonomously calling this tool, the action constitutes permanent data loss without user confirmation.
From the tool's definition Tool name is 'track_delete' with description 'Delete a track.' The verb 'Delete' is explicit and irreversible.
Documented attack patterns abuse exactly the kind of access track_delete gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and ReaperMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for track_delete:
{
"version": "1",
"default": "deny",
"hide": [
"track_delete"
]
}track_delete 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 track. It is categorised as a Destructive tool in the ReaperMCP 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 track_delete: 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 ReaperMCP. Nothing to install.
track_delete 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 track_delete 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 track_delete. 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.
track_delete is provided by the Reaper MCP server (xdarkzx/reaper-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from ReaperMCP, 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.
138 ReaperMCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.