This record as markdown: /tools/io-github-dreamrec-livepilot/check-flucoma.md
What check_flucoma does on Livepilot
AI agents call check_flucoma 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 check_flucoma is rated Low
This tool performs a read-only diagnostic check to verify installation and signal status of FluCoMa (a music analysis toolkit). It queries system state but does not create, modify, delete, or execute operations. No side effects or blast radius. Classification as Read is appropriate.
From the tool's definition Tool name 'check_flucoma' and description 'Check if FluCoMa is installed and sending data' indicate a diagnostic query operation that retrieves status information without modifying state.
Attacks that exploit this kind of access
The rule that runs check_flucoma 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 check_flucoma, this is the rule to start with:
check_flucoma 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 check_flucoma call is checked against it from then on.
Questions about check_flucoma
Check if FluCoMa is installed and sending data. 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 check_flucoma: 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.
check_flucoma 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 check_flucoma 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 check_flucoma. 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.
check_flucoma 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