This record as markdown: /tools/io-github-dreamrec-livepilot/stop-track-clips.md
What stop_track_clips does on Livepilot
AI agents invoke stop_track_clips 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 stop_track_clips is rated High
This tool executes a command that stops audio playback on a track—an external operation with effects determined by which track is targeted. It is not merely reading data (no Read), not creating/modifying persistent track data (not Write), and not destructive to data itself (not Destructive). The action is reversible (clips can be restarted), and there is no financial impact.
From the tool's definition Tool name 'stop_track_clips' and description 'Stop all playing clips on a track' indicate an action that triggers immediate state changes in Ableton Live's playback engine.
Attacks that exploit this kind of access
The rule that runs stop_track_clips 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 stop_track_clips, this is the rule to start with:
stop_track_clips 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 stop_track_clips call is checked against it from then on.
Questions about stop_track_clips
Stop all playing clips on a track. 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 stop_track_clips: 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.
stop_track_clips 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 stop_track_clips 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 stop_track_clips. 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.
stop_track_clips 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