stop_scrub

Stop scrubbing a clip. Call after scrub_clip to stop preview.

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-scrub.md

WHAT IT DOES

What stop_scrub does on Livepilot

AI agents invoke stop_scrub 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_scrub is rated High

This tool executes a command that changes the state of Ableton Live by stopping audio playback—a real-time operation dependent on prior state (scrub_clip must have been called). While it has no data side effects and is easily reversible, it qualifies as Execute rather than Write because it triggers an immediate external operation (audio preview halt) rather than persistently creating or modifying data.

From the tool's definition Tool performs an action ('Stop scrubbing') that triggers a state change in Ableton Live (halts audio playback preview).

Attacks that exploit this kind of access

RECOMMENDED RULE

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

stop_scrub Rate-limited

stop_scrub 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_scrub": {
      "limits": [
        {
          "counter": "stop_scrub_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_scrub call is checked against it from then on.

FAQ

Questions about stop_scrub

What does the stop_scrub tool do? +

Stop scrubbing a clip. Call after scrub_clip to stop preview. 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_scrub? +

Register the Livepilot MCP server in PolicyLayer and add a rule for stop_scrub: 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_scrub? +

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

Can I rate-limit stop_scrub? +

Yes. Add a rate_limit block to the stop_scrub 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_scrub completely? +

Set action: deny in the PolicyLayer policy for stop_scrub. 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_scrub? +

stop_scrub 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 →