Remove notes by clip id and note ids
AI agents call remove_notes_by_ids to permanently remove resources in Ableton Copilot MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
An AI agent that decides to call remove_notes_by_ids doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Ableton Copilot MCP is gone — there is no undo for destructive operations.
Attacks that exploit this kind of access
Remove notes by clip id and note ids. It is categorised as a Destructive tool in the Ableton Copilot MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Ableton Copilot MCP server in PolicyLayer and add a rule for remove_notes_by_ids: 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 Copilot MCP. Nothing to install.
remove_notes_by_ids 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_ids 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_ids. 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_ids is provided by the Ableton Copilot MCP server (xiaolaa2/ableton-copilot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.