New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

clear_simpler_slices

Remove all manual slices from the Simpler (Live 11+).

SERVERLivepilot SOURCElivepilot
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-dreamrec-livepilot/clear-simpler-slices.md

What clear_simpler_slices does on Livepilot

AI agents call clear_simpler_slices 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 clear_simpler_slices is rated Critical

This tool destroys user-created data (manual slice markers) in an audio sampler instrument without the ability to undo through the tool itself. The blast radius is significant for a music producer relying on those slices for their arrangement. While Ableton may have undo history, the tool's explicit purpose is permanent removal, making it Destructive rather than Write.

From the tool's definition "Remove all manual slices from the Simpler" — this action irreversibly deletes slices that a user has manually created in Ableton Live's Simpler instrument. The slices cannot be recovered without manual recreation.

Questions about clear_simpler_slices

What does the clear_simpler_slices tool do? +

Remove all manual slices from the Simpler (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.

How do I enforce a policy on clear_simpler_slices? +

Register the Livepilot MCP server in PolicyLayer and add a rule for clear_simpler_slices: 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.

What risk level is clear_simpler_slices? +

clear_simpler_slices is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit clear_simpler_slices? +

Yes. Add a rate_limit block to the clear_simpler_slices 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.

How do I block clear_simpler_slices completely? +

Set action: deny in the PolicyLayer policy for clear_simpler_slices. 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.

What MCP server provides clear_simpler_slices? +

clear_simpler_slices 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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Livepilot's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.