This record as markdown: /tools/io-github-dreamrec-livepilot/toggle-device-ab.md
What toggle_device_ab does on Livepilot
AI agents invoke toggle_device_ab 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 toggle_device_ab is rated High
This tool executes an action in Ableton Live (toggling A/B state on a device), which is an external operation with real effects on the running session. It's not a simple read, and while it modifies state, it's more of a triggered action/toggle than a conventional write. The effect is potentially reversible by toggling again, so it doesn't reach Destructive.
From the tool's definition 'Swap a device's A/B state' — triggers an external operation in Ableton Live that changes the active state of a device
Attacks that exploit this kind of access
The rule that runs toggle_device_ab 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 toggle_device_ab, this is the rule to start with:
toggle_device_ab 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 toggle_device_ab call is checked against it from then on.
Questions about toggle_device_ab
Swap a device's A/B state (Live 12.3+). 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 toggle_device_ab: 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.
toggle_device_ab 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 toggle_device_ab 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 toggle_device_ab. 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.
toggle_device_ab 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