AI agents call get_translations to retrieve information from Localise without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves translation data for viewing or analysis purposes. It queries existing translations without creating, modifying, deleting, or executing any operations. The blast radius of misuse is minimal—an agent could only view translations it is authorized to access, with no capability to alter data or trigger external effects.
From the tool's definition Tool name 'get_translations' and description 'Get all translations for a specific asset/key across all locales' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
Get all translations for a specific asset/key across all locales. It is categorised as a Read tool in the Localise MCP Server, which means it retrieves data without modifying state.
Register the Localise MCP server in PolicyLayer and add a rule for get_translations: 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 Localise. Nothing to install.
get_translations 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_translations 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_translations. 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_translations is provided by the Localise MCP server (localise-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →