stop_clip

Stop a playing clip.

SERVERLivepilot SOURCElivepilot

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-dreamrec-livepilot/stop-clip.md

WHAT IT DOES

What stop_clip does on Livepilot

AI agents invoke stop_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.

RISK

Why stop_clip is rated High

This tool executes a command to control Ableton Live's playback state. While the operation is reversible (clips can be restarted) and not destructive to data, it actively triggers an external system operation rather than merely reading or writing static data.

From the tool's definition Tool name 'stop_clip' and description 'Stop a playing clip' indicate an action that triggers an external operation (stopping audio playback in Ableton Live 12) whose effect depends on which clip argument is provided.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

stop_clip Rate-limited

stop_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.

View as policy code

policy.json

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

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Livepilot, apply this rule, and every stop_clip call is checked against it from then on.

FAQ

Questions about stop_clip

What does the stop_clip tool do? +

Stop a playing clip. 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.

How do I enforce a policy on stop_clip? +

Register the Livepilot MCP server in PolicyLayer and add a rule for stop_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.

What risk level is stop_clip? +

stop_clip is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit stop_clip? +

Yes. Add a rate_limit block to the stop_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.

How do I block stop_clip completely? +

Set action: deny in the PolicyLayer policy for stop_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.

What MCP server provides stop_clip? +

stop_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.

KEEP EXPLORING

More on Livepilot, and thousands of servers like it.

This server

All 474 Livepilot tools → High-risk tools on this server →

Across the catalogue

stop_emba_scan on EMBA-MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →