This record as markdown: /tools/io-github-dreamrec-livepilot/compare-to-reference.md
What compare_to_reference does on Livepilot
AI agents call compare_to_reference 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 compare_to_reference is rated Low
The name implies reading or comparing data against a reference point, typical of analysis tools in audio software. Without explicit side effects in the name or description, and given the sibling context (analyze_* tools are Read category), comparison operations are non-destructive reads. Low severity because comparisons have no blast radius on the project. Confidence reduced to 0.6 due to empty description.
From the tool's definition Tool name 'compare_to_reference' suggests a comparison/analysis operation without modification. Empty description limits certainty. Sibling tools show patterns: most are Write (add_*) or Read (analyze_*), positioning this as likely Read.
Attacks that exploit this kind of access
The rule that runs compare_to_reference 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 compare_to_reference, this is the rule to start with:
compare_to_reference 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 compare_to_reference call is checked against it from then on.
Questions about compare_to_reference
compare_to_reference 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 compare_to_reference: 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.
compare_to_reference 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 compare_to_reference 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 compare_to_reference. 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.
compare_to_reference 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