Delete a tempo/time-sig marker by its index (from tempo_list_markers).
AI agents call tempo_delete_marker 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.
This tool irreversibly deletes project data (tempo/time signature markers) that are integral to a music production file. Once deleted, recovery depends on manual undo or project backups. Deletion of critical timing markers could corrupt a project's arrangement or require significant rework. This meets the Destructive category definition of irreversibly deleting data that cannot be undone.
From the tool's definition Tool name contains 'delete' and description explicitly states 'Delete a tempo/time-sig marker by its index'. The action removes a marker from the REAPER project, which cannot be automatically undone if the agent deletes the wrong marker.
Documented attack patterns abuse exactly the kind of access tempo_delete_marker 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 tempo_delete_marker:
{
"version": "1",
"default": "deny",
"hide": [
"tempo_delete_marker"
]
}tempo_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 a tempo/time-sig marker by its index (from tempo_list_markers). 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 tempo_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 ReaperMCP. Nothing to install.
tempo_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 tempo_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 tempo_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.
tempo_delete_marker 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.