stop_all_clips

What stop_all_clips does on Livepilot

AI agents invoke stop_all_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_all_clips is rated High

This tool triggers an external operation (halting playback in Ableton Live) whose effects are immediate and depend on the session state. It is not merely reading data (Read), nor is it creating/modifying persistent data structures reversibly (Write). While the action is technically reversible by restarting clips, the tool itself executes a command with side effects on a live music production system.

From the tool's definition Tool named 'stop_all_clips' with description 'Stop all playing clips in the session. Panic button.' — performs an immediate, externally-observable action that stops audio playback across the entire session.

The rule that runs stop_all_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_all_clips, this is the rule to start with:

{
  "version": "1",
  "default": "deny",
  "tools": {
    "stop_all_clips": {
      "limits": [
        {
          "counter": "stop_all_clips_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

Questions about stop_all_clips