set_session_loop
Set loop on/off and optional loop region (start beat, length in beats).
This record as markdown: /tools/io-github-dreamrec-livepilot/set-session-loop.md
What set_session_loop does on Livepilot
AI agents use set_session_loop 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 set_session_loop is rated Medium
This tool writes/updates playback loop settings (enabled state and region boundaries) in Ableton Live. It is reversible (loop can be toggled back or region changed), has no destructive or financial implications, and its blast radius is minimal — at worst it disrupts a loop region during a session.
From the tool's definition 'Set loop on/off and optional loop region (start beat, length in beats)' — modifies loop state and region parameters
Attacks that exploit this kind of access
The rule that runs set_session_loop 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 set_session_loop, this is the rule to start with:
set_session_loop 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 set_session_loop call is checked against it from then on.
Questions about set_session_loop
Set loop on/off and optional loop region (start beat, length in beats). 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 set_session_loop: 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.
set_session_loop 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 set_session_loop 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 set_session_loop. 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.
set_session_loop 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