This record as markdown: /tools/io-github-dreamrec-livepilot/fire-scene-clips.md
What fire_scene_clips does on Livepilot
AI agents invoke fire_scene_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 fire_scene_clips is rated High
In Ableton Live, 'firing' a scene means launching all clips in that scene simultaneously, triggering external audio/MIDI playback operations. This is an Execute-category action as it triggers operations in an external system. The description is empty, so confidence is reduced, but the name is highly indicative of this behavior in the context of an Ableton Live MCP server.
From the tool's definition Tool name 'fire_scene_clips' — 'fire' strongly implies triggering/launching scene clips in Ableton Live, which is an external operation that starts playback of clips
Attacks that exploit this kind of access
The rule that runs fire_scene_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 fire_scene_clips, this is the rule to start with:
fire_scene_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 fire_scene_clips call is checked against it from then on.
Questions about fire_scene_clips
fire_scene_clips is a execute tool on the Livepilot MCP server. 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 fire_scene_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.
fire_scene_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 fire_scene_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 fire_scene_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.
fire_scene_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