import_slices_from_onsets
Force Transient slicing mode, set sensitivity, and re-detect (Live 11+).
This record as markdown: /tools/io-github-dreamrec-livepilot/import-slices-from-onsets.md
What import_slices_from_onsets does on Livepilot
AI agents invoke import_slices_from_onsets to trigger actions in Livepilot. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why import_slices_from_onsets is rated High
This tool both changes configuration (slicing mode, sensitivity) and triggers an active operation (re-detect), making it an Execute action. It modifies state in Ableton Live but the effects are reversible (slicing modes can be changed), so it doesn't rise to Destructive. Misuse could corrupt slice points in a project but is generally recoverable.
From the tool's definition Force Transient slicing mode, set sensitivity, and re-detect — triggers an active re-detection/analysis operation and modifies slicing mode settings
Attacks that exploit this kind of access
The rule that runs import_slices_from_onsets 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 import_slices_from_onsets, this is the rule to start with:
import_slices_from_onsets stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Livepilot, apply this rule, and every import_slices_from_onsets call is checked against it from then on.
Questions about import_slices_from_onsets
Force Transient slicing mode, set sensitivity, and re-detect (Live 11+). It is categorised as a Execute tool in the Livepilot MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Livepilot MCP server in PolicyLayer and add a rule for import_slices_from_onsets: 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.
import_slices_from_onsets is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the import_slices_from_onsets 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 import_slices_from_onsets. 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.
import_slices_from_onsets 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