capture_and_insert_scene
Capture currently-playing clips and insert them as a new scene. Distinct from capture_midi.
This record as markdown: /tools/io-github-dreamrec-livepilot/capture-and-insert-scene.md
What capture_and_insert_scene does on Livepilot
AI agents use capture_and_insert_scene to create or update resources in Livepilot, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Livepilot environment.
Why capture_and_insert_scene is rated Medium
This tool creates a new scene by capturing and inserting clips, which modifies the project structure reversibly. While it alters the state of the Ableton Live document, the operation is not destructive (scenes can be deleted or modified later) and does not execute arbitrary code or trigger external operations.
From the tool's definition Tool description states it will 'capture currently-playing clips and insert them as a new scene.' The verb 'insert' indicates creation of a new data structure (a scene) in the Ableton Live project.
Attacks that exploit this kind of access
The rule that runs capture_and_insert_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 capture_and_insert_scene, this is the rule to start with:
capture_and_insert_scene stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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 capture_and_insert_scene call is checked against it from then on.
Questions about capture_and_insert_scene
Capture currently-playing clips and insert them as a new scene. Distinct from capture_midi. It is categorised as a Write tool in the Livepilot MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Livepilot MCP server in PolicyLayer and add a rule for capture_and_insert_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.
capture_and_insert_scene is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the capture_and_insert_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 capture_and_insert_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.
capture_and_insert_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.
This server
Across the catalogue