AI agents call marker_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.
The tool permanently removes markers/regions from an audio project with no undo capability exposed through the MCP interface. While markers are metadata rather than audio content, their deletion is irreversible and could corrupt project organization, cue points, or arrangement structure. This qualifies as Destructive (irreversible deletion) rather than Write (reversible modification).
From the tool's definition Tool name 'marker_delete' with description 'Delete marker/region' explicitly performs irreversible deletion of markers or regions in a REAPER project.
Documented attack patterns abuse exactly the kind of access marker_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 marker_delete:
{
"version": "1",
"default": "deny",
"hide": [
"marker_delete"
]
} marker_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 marker/region. 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 marker_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.
marker_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 marker_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 marker_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.
marker_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.