atlas_compare
Compare two devices — strengths, weaknesses, and recommendation for a role.
This record as markdown: /tools/io-github-dreamrec-livepilot/atlas-compare.md
What atlas_compare does on Livepilot
AI agents call atlas_compare 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_compare is rated Low
This tool retrieves and analyzes information about devices in Ableton Live without altering any state. It falls squarely into the Read category as it queries and compares existing device properties to provide recommendations. The low severity reflects minimal blast radius—misuse would only return inappropriate comparisons, not cause data loss or unwanted modifications.
From the tool's definition The tool 'atlas_compare' performs a comparison operation between two devices, returning analysis of 'strengths, weaknesses, and recommendation for a role.' This is a query/analysis function with no modification, creation, deletion, or execution of…
Attacks that exploit this kind of access
The rule that runs atlas_compare 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_compare, this is the rule to start with:
atlas_compare 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_compare call is checked against it from then on.
Questions about atlas_compare
Compare two devices — strengths, weaknesses, and recommendation for a role. 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_compare: 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_compare 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_compare 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_compare. 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_compare 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