item_take_delete_active

THE RISK

Critical Risk

Why item_take_delete_active needs a policy

The tool explicitly deletes a take (audio/MIDI recording segment) from a project item. Deletion of recorded audio/MIDI takes is irreversible and cannot be undone without a prior undo history, making this Destructive. The blast radius is high because a misused call could permanently remove recorded musical content.

From the tool's definition Delete the currently active take from an item

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

POLICY

How to control item_take_delete_active

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

policy.json

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

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

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 item_take_delete_active

What does the item_take_delete_active tool do? +

Delete the currently active take from an item. 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 item_take_delete_active? +

Register the Reaper MCP server in PolicyLayer and add a rule for item_take_delete_active: 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 item_take_delete_active? +

item_take_delete_active 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 item_take_delete_active? +

Yes. Add a rate_limit block to the item_take_delete_active 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 item_take_delete_active completely? +

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

item_take_delete_active 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 →