This record as markdown: /tools/io-github-dreamrec-livepilot/atlas-device-info.md
What atlas_device_info does on Livepilot
AI agents call atlas_device_info 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 atlas_device_info is rated Low
The suffix '_info' strongly implies a read-only query operation that retrieves or exposes information about a device. Without a description, confidence is moderate, but the lack of action verbs (add, set, delete, trigger) and the informational nature of 'info' endpoints point to Read category. Blast radius is low—retrieving device metadata poses minimal risk.
From the tool's definition Tool name 'atlas_device_info' indicates retrieval of device information. No description provided, but the naming pattern and context (AI copilot for Ableton Live) suggest querying metadata about Atlas devices rather than modifying state.
Attacks that exploit this kind of access
The rule that runs atlas_device_info 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 atlas_device_info, this is the rule to start with:
atlas_device_info 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 atlas_device_info call is checked against it from then on.
Questions about atlas_device_info
atlas_device_info 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 atlas_device_info: 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.
atlas_device_info 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 atlas_device_info 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 atlas_device_info. 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.
atlas_device_info 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