remove_arrangement_notes
Remove all MIDI notes in a pitch/time region of an arrangement clip. Defaults remove ALL notes.
This record as markdown: /tools/io-github-dreamrec-livepilot/remove-arrangement-notes.md
What remove_arrangement_notes does on Livepilot
AI agents call remove_arrangement_notes to permanently remove resources in Livepilot, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why remove_arrangement_notes is rated Critical
This tool permanently deletes MIDI note data from an arrangement clip without reversibility. While the context is music production (Ableton Live), the destructive nature of removing all notes in a region—especially with the potential to wipe an entire clip if defaults are used—poses a high risk of data loss and workflow disruption.
From the tool's definition The tool 'remove_arrangement_notes' explicitly 'Remove[s] all MIDI notes in a pitch/time region' with the description noting that defaults 'remove ALL notes.' This is an irreversible deletion of musical data.
Attacks that exploit this kind of access
The rule that runs remove_arrangement_notes safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Livepilot, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For remove_arrangement_notes, this is the rule to start with:
remove_arrangement_notes is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Livepilot, apply this rule, and every remove_arrangement_notes call is checked against it from then on.
Questions about remove_arrangement_notes
Remove all MIDI notes in a pitch/time region of an arrangement clip. Defaults remove ALL notes. It is categorised as a Destructive tool in the Livepilot MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Livepilot MCP server in PolicyLayer and add a rule for remove_arrangement_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 Livepilot. Nothing to install.
remove_arrangement_notes 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 remove_arrangement_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.
Set action: deny in the PolicyLayer policy for remove_arrangement_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.
remove_arrangement_notes is provided by the Livepilot MCP server (livepilot). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Livepilot, and thousands of servers like it.
Across the catalogue