tempo_clear_all

THE RISK

Critical Risk

Why tempo_clear_all needs a policy

This tool permanently removes all tempo and time signature markers from a REAPER project without the ability to selectively recover individual markers. In music production, tempo and time signature markers are critical structural elements; deleting all of them irreversibly destroys essential project metadata that would require manual reconstruction.

From the tool's definition Tool description explicitly states 'Delete every tempo/time-sig marker' and 'resets the project to its base tempo.' The verb 'Delete' combined with 'every' indicates irreversible removal of all tempo and time signature markers from the project.

Risk signalsBulk/mass operation — affects multiple targets

Documented attack patterns abuse exactly the kind of access tempo_clear_all gives an agent:

POLICY

How to control tempo_clear_all

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_clear_all:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "tempo_clear_all"
  ]
}

tempo_clear_all disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register ReaperMCP — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More ReaperMCP tools

Destructive envelope_clear_range envelope_clear_range Destructive fx_remove Remove FX from track chain. Destructive item_delete Delete an item. Destructive marker_delete Delete marker/region. Destructive midi_delete_all_notes Clear all notes from a MIDI item. Destructive midi_delete_cc Delete a CC event. Destructive midi_delete_note Delete a note. Destructive tempo_delete_marker Delete a tempo/time-sig marker by its index (from tempo_list_markers).

All 138 ReaperMCP tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in ReaperMCP → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about tempo_clear_all

What does the tempo_clear_all tool do? +

Delete every tempo/time-sig marker — resets the project to its base tempo. 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.

How do I enforce a policy on tempo_clear_all? +

Register the Reaper MCP server in PolicyLayer and add a rule for tempo_clear_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 ReaperMCP. Nothing to install.

What risk level is tempo_clear_all? +

tempo_clear_all is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit tempo_clear_all? +

Yes. Add a rate_limit block to the tempo_clear_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.

How do I block tempo_clear_all completely? +

Set action: deny in the PolicyLayer policy for tempo_clear_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.

What MCP server provides tempo_clear_all? +

tempo_clear_all 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.

Enforce policy on every ReaperMCP tool call.

Start from ReaperMCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →