delete_clip
Delete a clip from a clip slot. This removes all notes and automation. Use undo to revert.
This record as markdown: /tools/io-github-dreamrec-livepilot/delete-clip.md
What delete_clip does on Livepilot
AI agents call delete_clip 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 delete_clip is rated Critical
This tool irreversibly deletes user-created musical content (notes and automation data) from an Ableton Live clip. While undo is available as a recovery mechanism, the primary action is destructive data removal. In the context of an AI agent operating Ableton Live autonomously, accidental deletion of clips could result in significant loss of creative work.
From the tool's definition The tool 'delete_clip' performs deletion that 'removes all notes and automation' from a clip. The description explicitly acknowledges this is irreversible ('Use undo to revert'), confirming the data loss is permanent without external intervention.
Attacks that exploit this kind of access
The rule that runs delete_clip 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 delete_clip, this is the rule to start with:
delete_clip 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 delete_clip call is checked against it from then on.
Questions about delete_clip
Delete a clip from a clip slot. This removes all notes and automation. 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 delete_clip: 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.
delete_clip 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 delete_clip 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 delete_clip. 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.
delete_clip 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