This record as markdown: /tools/io-github-dreamrec-livepilot/get-device-ab-state.md
What get_device_ab_state does on Livepilot
AI agents call get_device_ab_state to retrieve information from Livepilot without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_device_ab_state is rated Low
This tool retrieves the A/B comparison state of an Ableton Live device, which is a non-destructive query operation. It does not modify, create, delete, or execute any operations—it only reads and returns existing state information. The low severity reflects minimal risk even if misused, as reading device parameters cannot cause harm to the project or system.
From the tool's definition Tool name contains 'get_' prefix and description explicitly states 'Read a device's A/B compare state'. The verb 'Read' combined with querying a state value indicates data retrieval with no side effects.
Attacks that exploit this kind of access
The rule that runs get_device_ab_state 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 get_device_ab_state, this is the rule to start with:
get_device_ab_state is read-only, so it stays allowed. 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 get_device_ab_state call is checked against it from then on.
Questions about get_device_ab_state
Read a device's A/B compare state (Live 12.3+). It is categorised as a Read tool in the Livepilot MCP Server, which means it retrieves data without modifying state.
Register the Livepilot MCP server in PolicyLayer and add a rule for get_device_ab_state: 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.
get_device_ab_state is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_device_ab_state 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 get_device_ab_state. 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.
get_device_ab_state 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