set_simpler_playback_mode
Set Simpler's playback mode. playback_mode: 0=Classic, 1=One-Shot, 2=Slice. slice_by (Slice only): 0=Transient, 1=Beat, 2=Region, 3=Manual. sensitivity (0.0-1.0, Transient only).
This record as markdown: /tools/io-github-dreamrec-livepilot/set-simpler-playback-mode.md
What set_simpler_playback_mode does on Livepilot
AI agents use set_simpler_playback_mode 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_simpler_playback_mode is rated Medium
This is a configuration write operation that changes the playback mode and slicing behavior of Ableton's Simpler instrument. While it reverses the change (playback mode can be switched back), the modification of instrument parameters and the potential for the AI to misapply settings could affect the user's project state or workflow.
From the tool's definition Tool sets Simpler's playback mode to one of three options (Classic, One-Shot, or Slice) and optionally configures slice parameters (slice_by and sensitivity). This modifies the instrument's configuration state within Ableton Live.
Attacks that exploit this kind of access
The rule that runs set_simpler_playback_mode 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_simpler_playback_mode, this is the rule to start with:
set_simpler_playback_mode 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_simpler_playback_mode call is checked against it from then on.
Questions about set_simpler_playback_mode
Set Simpler's playback mode. playback_mode: 0=Classic, 1=One-Shot, 2=Slice. slice_by (Slice only): 0=Transient, 1=Beat, 2=Region, 3=Manual. sensitivity (0.0-1.0, Transient only). 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_simpler_playback_mode: 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_simpler_playback_mode 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_simpler_playback_mode 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_simpler_playback_mode. 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_simpler_playback_mode 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