get_chroma
Get 12 pitch class energies from FluCoMa for real-time chord detection.
This record as markdown: /tools/io-github-dreamrec-livepilot/get-chroma.md
What get_chroma does on Livepilot
AI agents call get_chroma 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 get_chroma is rated Low
This tool queries and returns computed audio feature data (chroma/pitch class energy) for analysis purposes. It reads real-time audio state from Ableton Live but does not create, modify, delete, or execute arbitrary operations. No side effects or irreversible changes are possible. Severity is low because misuse merely returns analysis data that cannot cause harm to the music project or external systems.
From the tool's definition Tool name 'get_chroma' and description 'Get 12 pitch class energies' indicate retrieval of real-time audio analysis data.
Attacks that exploit this kind of access
The rule that runs get_chroma 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 get_chroma, this is the rule to start with:
get_chroma 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 get_chroma call is checked against it from then on.
Questions about get_chroma
Get 12 pitch class energies from FluCoMa for real-time chord detection. 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 get_chroma: 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.
get_chroma 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 get_chroma 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 get_chroma. 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.
get_chroma 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