Critical Risk →

remove_all_notes

Remove all notes from a clip.

How to control remove_all_notes ↓

What remove_all_notes does on Ableton

AI agents call remove_all_notes to permanently remove resources in Ableton — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why remove_all_notes needs a policy

This tool performs an irreversible operation that permanently deletes all note data from a clip without the ability to undo through the tool itself. While Ableton Live may have an undo function, the tool's primary action is destructive data removal. The loss of composed musical notes cannot be recovered through the tool's own mechanism, making this a Destructive action rather than merely Write.

From the tool's definition Tool name 'remove_all_notes' and description 'Remove all notes from a clip' indicate irreversible deletion of musical data.

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

How to control remove_all_notes

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

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "remove_all_notes"
  ]
}

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

  1. Create a free account and register Ableton — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about remove_all_notes

What does the remove_all_notes tool do? +

Remove all notes from a clip. It is categorised as a Destructive tool in the Ableton 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 remove_all_notes? +

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

What risk level is remove_all_notes? +

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

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

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

remove_all_notes is provided by the Ableton MCP server (jpoindexter/ableton-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Ableton tool call.

Start from Ableton, 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.

128 Ableton tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.