AI agents call track_fx_delete 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.
Deleting an FX plugin from a track removes it and its configuration permanently (within the session unless manually undone). This constitutes an irreversible destructive action — the plugin's state, settings, and any associated envelopes are lost. In a production workflow, this could destroy hours of careful configuration.
From the tool's definition 'Remove an FX plugin from a track' — removal of a plugin is irreversible without an explicit undo step, destroying the plugin's state, parameter settings, and automation associations.
Documented attack patterns abuse exactly the kind of access track_fx_delete 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 track_fx_delete:
{
"version": "1",
"default": "deny",
"hide": [
"track_fx_delete"
]
}track_fx_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.
Remove an FX plugin from a track. 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 track_fx_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 Reaper. Nothing to install.
track_fx_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_fx_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_fx_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_fx_delete 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.