This record as markdown: /tools/io-github-dreamrec-livepilot/fire-scene.md
What fire_scene does on Livepilot
AI agents invoke fire_scene 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 is rated High
This tool triggers external operations in Ableton Live — launching a scene causes all clips in that scene to start playing. This is an Execute-category action as it triggers real-time playback operations whose effects depend on which scene is targeted. It doesn't read data, write/modify stored data, delete anything, or move money, but it does trigger a live external operation.
From the tool's definition Fire (launch) a scene, triggering all its clips
Attacks that exploit this kind of access
The rule that runs fire_scene 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, this is the rule to start with:
fire_scene 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 call is checked against it from then on.
Questions about fire_scene
Fire (launch) a scene, triggering all its clips. 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: 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 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 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. 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 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