This record as markdown: /tools/io-github-dreamrec-livepilot/get-mix-issues.md
What get_mix_issues does on Livepilot
AI agents invoke get_mix_issues to trigger actions in Livepilot. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why get_mix_issues is rated High
The description says it 'runs' mix critics, implying active execution of analysis routines. While the output is read-only (returning detected issues), the act of triggering multiple critic processes is closer to Execute than Read. Misuse risk is medium since it only returns analysis results with no data modification, but it does trigger computational processes whose scope depends on the current session state.
From the tool's definition 'Run all mix critics' — the tool actively runs/executes analysis processes rather than simply retrieving stored data
Attacks that exploit this kind of access
The rule that runs get_mix_issues 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_mix_issues, this is the rule to start with:
get_mix_issues stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. 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_mix_issues call is checked against it from then on.
Questions about get_mix_issues
Run all mix critics and return detected issues only. It is categorised as a Execute tool in the Livepilot MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Livepilot MCP server in PolicyLayer and add a rule for get_mix_issues: 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_mix_issues is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the get_mix_issues 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_mix_issues. 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_mix_issues 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.
Across the catalogue