This record as markdown: /tools/io-github-dreamrec-livepilot/verify-device-alive.md
What verify_device_alive does on Livepilot
AI agents call verify_device_alive 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 verify_device_alive is rated Low
The verb 'verify' combined with 'device_alive' indicates this tool likely queries whether an Ableton Live device is active or responsive, with no side effects. This is a read operation—it retrieves device status without modifying state. Confidence is moderate (0.65) because the description is empty, so classification relies entirely on the name.
From the tool's definition Tool name 'verify_device_alive' suggests a status check or query operation. The name structure (verify/check) indicates a read-only diagnostic action.
Attacks that exploit this kind of access
The rule that runs verify_device_alive 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 verify_device_alive, this is the rule to start with:
verify_device_alive 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 verify_device_alive call is checked against it from then on.
Questions about verify_device_alive
verify_device_alive is a read tool on the Livepilot MCP server. 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 verify_device_alive: 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.
verify_device_alive 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 verify_device_alive 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 verify_device_alive. 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.
verify_device_alive 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