This record as markdown: /tools/io-github-dreamrec-livepilot/analyze-harmony.md
What analyze_harmony does on Livepilot
AI agents call analyze_harmony 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 analyze_harmony is rated Low
Despite empty description, the name and pattern of sibling analysis tools ('analyze_*') suggest read-only inspection of existing music data. No mutation, deletion, execution, or financial operation is implied. The 'analyze' prefix strongly indicates a query/retrieval operation that examines harmonic properties without side effects.
From the tool's definition Tool name 'analyze_harmony' and context of sibling tools ('analyze_composition', 'analyze_for_automation') indicate this performs analysis/querying of harmonic content in Ableton Live 12 without modifying data.
Attacks that exploit this kind of access
The rule that runs analyze_harmony 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 analyze_harmony, this is the rule to start with:
analyze_harmony 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 analyze_harmony call is checked against it from then on.
Questions about analyze_harmony
analyze_harmony 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 analyze_harmony: 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.
analyze_harmony 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 analyze_harmony 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 analyze_harmony. 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.
analyze_harmony 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