clear_fx_envelope

THE RISK

Critical Risk

Why clear_fx_envelope needs a policy

The word 'clear' combined with 'all automation points' indicates irreversible deletion of envelope data. Removing all automation points from an FX parameter envelope cannot be undone through the tool itself, making this a destructive operation with high blast radius since it wipes the entire automation envelope for an FX parameter.

From the tool's definition Clear all automation points from an FX parameter envelope

Risk signalsBulk/mass operation — affects multiple targets

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

POLICY

How to control clear_fx_envelope

PolicyLayer is an MCP gateway — it sits between your AI agents and Reaper, and nothing reaches the server without passing your rules. This is the rule we recommend for clear_fx_envelope:

policy.json

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

clear_fx_envelope 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 Reaper — 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 Reaper tools

Destructive clear_envelope Delete all points from an envelope. Destructive clear_midi_item Delete all MIDI notes from an item. Destructive delete_envelope_point Delete an envelope point. Destructive delete_fx_envelope_point delete_fx_envelope_point Destructive delete_item Delete a media item. Destructive delete_marker Delete a marker by index. Destructive delete_midi_note Delete a MIDI note from an item. Destructive delete_region Delete a region by index.

All 158 Reaper 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 Reaper → 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 clear_fx_envelope

What does the clear_fx_envelope tool do? +

Clear all automation points from an FX parameter envelope. It is categorised as a Destructive tool in the Reaper 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 clear_fx_envelope? +

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

What risk level is clear_fx_envelope? +

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

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

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

clear_fx_envelope is provided by the Reaper MCP server (twelvetake-studios/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 Reaper tool call.

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

CHECK YOUR STACK →