set_exclusive_arm
Enable/disable exclusive arm mode (only one track armed at a time).
This record as markdown: /tools/io-github-dreamrec-livepilot/set-exclusive-arm.md
What set_exclusive_arm does on Livepilot
AI agents use set_exclusive_arm 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_exclusive_arm is rated Medium
This tool modifies the arming behavior of tracks in Ableton Live, which is a reversible state change (exclusive arm mode can be toggled on or off). It does not execute code, delete data, or move money. It falls under Write because it changes application settings/state.
From the tool's definition The tool description states it will 'Enable/disable exclusive arm mode', which modifies a configuration setting in Ableton Live. This is a state change that affects which tracks can be armed for recording.
Attacks that exploit this kind of access
The rule that runs set_exclusive_arm 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_exclusive_arm, this is the rule to start with:
set_exclusive_arm 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_exclusive_arm call is checked against it from then on.
Questions about set_exclusive_arm
Enable/disable exclusive arm mode (only one track armed at a time). 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_exclusive_arm: 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_exclusive_arm 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_exclusive_arm 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_exclusive_arm. 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_exclusive_arm 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