This record as markdown: /tools/io-github-dreamrec-livepilot/delete-rack-variation.md
What delete_rack_variation does on Livepilot
AI agents call delete_rack_variation 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_rack_variation is rated Critical
This tool irreversibly deletes data (a Rack variation) and cannot be undone programmatically. While the blast radius is limited to a single variation within a music project rather than the entire project, deletion of user-created content is inherently destructive. Classified as Destructive rather than Write because the operation cannot be reversed and results in permanent data loss.
From the tool's definition Tool name contains 'delete' and description states 'Delete a Rack variation by index'. The action permanently removes a Rack variation object from Ableton Live.
Attacks that exploit this kind of access
The rule that runs delete_rack_variation 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_rack_variation, this is the rule to start with:
delete_rack_variation 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_rack_variation call is checked against it from then on.
Questions about delete_rack_variation
Delete a Rack variation by index (Live 11+). 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_rack_variation: 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_rack_variation 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_rack_variation 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_rack_variation. 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_rack_variation 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