get_translation_issues
Get just the translation issues without the full report.
This record as markdown: /tools/io-github-dreamrec-livepilot/get-translation-issues.md
What get_translation_issues does on Livepilot
AI agents call get_translation_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_translation_issues is rated Low
This is a diagnostic or analysis tool that retrieves and reports translation issues from Ableton Live 12's project state. It performs a read-only query with no side effects, no code execution, no data modification, and no irreversible actions. The low severity reflects that misuse would only expose diagnostic information about translation problems, with no destructive or operational impact on the music project.
From the tool's definition Tool name 'get_translation_issues' and description 'Get just the translation issues without the full report' indicate a retrieval operation that queries and returns information without modifying, executing, or deleting anything.
Attacks that exploit this kind of access
The rule that runs get_translation_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_translation_issues, this is the rule to start with:
get_translation_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_translation_issues call is checked against it from then on.
Questions about get_translation_issues
Get just the translation issues without the full report. 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_translation_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_translation_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_translation_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_translation_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_translation_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