get_sound_design_issues
Run all sound design critics and return detected issues only.
This record as markdown: /tools/io-github-dreamrec-livepilot/get-sound-design-issues.md
What get_sound_design_issues does on Livepilot
AI agents call get_sound_design_issues 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_sound_design_issues is rated Low
This is a diagnostic/analysis tool that retrieves and reports information about sound design quality in an Ableton Live project. It performs no modifications to the project state, executes no external commands, and causes no side effects. The word 'run' refers to running analysis logic, not arbitrary code execution. Classification: Read.
From the tool's definition Tool name and description indicate it 'Run all sound design critics and return detected issues only' — it analyzes and reports on existing sound design without modifying, deleting, or executing external operations.
Attacks that exploit this kind of access
The rule that runs get_sound_design_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_sound_design_issues, this is the rule to start with:
get_sound_design_issues 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_sound_design_issues call is checked against it from then on.
Questions about get_sound_design_issues
Run all sound design critics and return detected issues only. 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_sound_design_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_sound_design_issues 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_sound_design_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_sound_design_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_sound_design_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.
This server
Across the catalogue