remove_notes_by_id
Remove specific MIDI notes by their IDs (JSON array of ints). Use undo to revert.
This record as markdown: /tools/io-github-dreamrec-livepilot/remove-notes-by-id.md
What remove_notes_by_id does on Livepilot
AI agents call remove_notes_by_id 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_by_id is rated Critical
Removing MIDI notes permanently alters a user's composition/project state. While undo exists, the tool's core function is irreversible deletion of data elements (notes). This is destructive rather than merely Write because it destroys existing musical content. The high severity reflects that an AI agent misusing this could delete large portions of a user's work.
From the tool's definition Tool removes/deletes MIDI notes by ID, an irreversible operation on music data. Description explicitly states 'Remove' and references undo as the reversion mechanism, indicating the primary action is destructive rather than reversible write.
Attacks that exploit this kind of access
The rule that runs remove_notes_by_id 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_by_id, this is the rule to start with:
remove_notes_by_id 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_by_id call is checked against it from then on.
Questions about remove_notes_by_id
Remove specific MIDI notes by their IDs (JSON array of ints). Use undo to revert. 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_by_id: 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_by_id 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_by_id 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_by_id. 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_by_id 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