stop_playback
Stop playback — halts the session transport and the arrangement cursor returns to its last position.
This record as markdown: /tools/io-github-dreamrec-livepilot/stop-playback.md
What stop_playback does on Livepilot
AI agents invoke stop_playback 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_playback is rated High
This tool executes a command that controls Ableton Live's transport layer. While the action is reversible (playback can be resumed) and has minimal blast radius in isolation, it matches the Execute category because it triggers an external operation on the DAW.
From the tool's definition Tool description states 'Stop playback — halts the session transport and the arrangement cursor returns to its last position.' This triggers an external operation (transport control) on Ableton Live 12 whose effects depend on the current playback state.
Attacks that exploit this kind of access
The rule that runs stop_playback 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_playback, this is the rule to start with:
stop_playback 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_playback call is checked against it from then on.
Questions about stop_playback
Stop playback — halts the session transport and the arrangement cursor returns to its last 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 stop_playback: 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_playback 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_playback 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_playback. 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_playback 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