get_appointed_device
Return the Blue Hand (appointed/focused) device location as (track_index, device_index, track_name, device_name).
This record as markdown: /tools/io-github-dreamrec-livepilot/get-appointed-device.md
What get_appointed_device does on Livepilot
AI agents call get_appointed_device 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_appointed_device is rated Low
This tool only retrieves information about the currently-focused device's location and name. It performs no modifications, deletions, code execution, or financial operations. It is a straightforward data retrieval call with no side effects, fitting the 'Read' category. The low severity reflects that exposing this query poses minimal risk even if misused by an AI agent.
From the tool's definition Tool name is 'get_appointed_device' with verb 'get'; description states 'Return the Blue Hand (appointed/focused) device location' — a pure query operation that retrieves the current state of which device has focus in Ableton Live.
Attacks that exploit this kind of access
The rule that runs get_appointed_device 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_appointed_device, this is the rule to start with:
get_appointed_device 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_appointed_device call is checked against it from then on.
Questions about get_appointed_device
Return the Blue Hand (appointed/focused) device location as (track_index, device_index, track_name, device_name). 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_appointed_device: 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_appointed_device 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_appointed_device 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_appointed_device. 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_appointed_device 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