remove_notes
Remove all MIDI notes in a pitch/time region. Use undo to revert. Defaults remove ALL notes in the clip.
This record as markdown: /tools/io-github-dreamrec-livepilot/remove-notes.md
What remove_notes does on Livepilot
AI agents call remove_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_notes is rated Critical
This tool irreversibly deletes MIDI note data from a music clip. While technically undoable via Ableton's undo feature, the primary action is deletion of user data without explicit per-note confirmation. An AI agent with loose parameters could delete extensive musical work in a single call. This is Destructive rather than Write because it permanently removes data (no reversible modification).
From the tool's definition Tool description explicitly states 'Remove all MIDI notes' and 'Defaults remove ALL notes in the clip.' The mention of 'Use undo to revert' acknowledges the destructive nature but does not change the irreversible-by-default behavior.
Attacks that exploit this kind of access
The rule that runs remove_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_notes, this is the rule to start with:
remove_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_notes call is checked against it from then on.
Questions about remove_notes
Remove all MIDI notes in a pitch/time region. Use undo to revert. Defaults remove ALL notes in the clip. 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_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_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_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_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_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