AI agents call dsl_track_delete_all to permanently remove resources in REAPER MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting all tracks in a REAPER project irreversibly removes audio data and project structure that cannot be easily recovered. This is a destructive operation with significant blast radius if triggered by an AI agent without user intent. The lack of description is noted but the name leaves no ambiguity about the destructive nature of the action.
From the tool's definition Tool name 'dsl_track_delete_all' explicitly indicates deletion of all tracks with no description provided to suggest otherwise. The verb 'delete' combined with 'all' is a clear destructive operation.
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access dsl_track_delete_all gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and REAPER MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for dsl_track_delete_all:
{
"version": "1",
"default": "deny",
"hide": [
"dsl_track_delete_all"
]
}dsl_track_delete_all 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.
dsl_track_delete_all. It is categorised as a Destructive tool in the REAPER MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the REAPER MCP Server MCP server in PolicyLayer and add a rule for dsl_track_delete_all: 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 MCP Server. Nothing to install.
dsl_track_delete_all 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 dsl_track_delete_all 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 dsl_track_delete_all. 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.
dsl_track_delete_all is provided by the REAPER MCP Server MCP server (shiehn/total-reaper-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 45 REAPER MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
45 REAPER MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.