AI agents call delete_marker 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_marker' function performs an irreversible delete operation on markers in REAPER. While markers are typically less critical than audio items or regions, deletion cannot be undone programmatically through this tool and represents permanent loss of project metadata. This fits the Destructive category (irreversibly deletes data).
From the tool's definition Tool name 'delete_marker' combined with sibling destructive operations (delete_item, delete_region) and the overall REAPER DAW control context indicate irreversible deletion functionality.
Documented attack patterns abuse exactly the kind of access delete_marker 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_marker:
{
"version": "1",
"default": "deny",
"hide": [
"delete_marker"
]
}delete_marker 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. 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_marker: 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_marker 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_marker 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_marker. 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_marker 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.