This record as markdown: /tools/io-github-dreamrec-livepilot/scrub-clip.md
What scrub_clip does on Livepilot
AI agents invoke scrub_clip 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 scrub_clip is rated High
This tool triggers a playback action in Ableton Live (scrubbing/previewing a clip), which is an external operation that causes the DAW to play audio at a given position. It doesn't read/write data persistently, but it does trigger an external operation in the application. Severity is low as it only affects audio preview with no lasting data changes.
From the tool's definition Scrub/preview a clip at a specific beat position
Attacks that exploit this kind of access
The rule that runs scrub_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 scrub_clip, this is the rule to start with:
scrub_clip 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 scrub_clip call is checked against it from then on.
Questions about scrub_clip
Scrub/preview a clip at a specific beat position. 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 scrub_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.
scrub_clip 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 scrub_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 scrub_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.
scrub_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