splice_remove_from_collection
Remove one or more samples from a user Collection (server-side).
This record as markdown: /tools/io-github-dreamrec-livepilot/splice-remove-from-collection.md
What splice_remove_from_collection does on Livepilot
AI agents call splice_remove_from_collection 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 splice_remove_from_collection is rated Critical
The tool explicitly removes samples from a collection on the server side. Removal of items from a collection is a destructive operation — it cannot be trivially undone and may result in permanent loss of curated data. The blast radius is high because an AI agent could inadvertently remove multiple samples from a user's carefully curated collection.
From the tool's definition Remove one or more samples from a user Collection (server-side)
Attacks that exploit this kind of access
The rule that runs splice_remove_from_collection 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 splice_remove_from_collection, this is the rule to start with:
splice_remove_from_collection 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 splice_remove_from_collection call is checked against it from then on.
Questions about splice_remove_from_collection
Remove one or more samples from a user Collection (server-side). 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 splice_remove_from_collection: 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.
splice_remove_from_collection 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 splice_remove_from_collection 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 splice_remove_from_collection. 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.
splice_remove_from_collection 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