AI agents call translate to retrieve information from Lara without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only translation operation on input text. It retrieves translation data from memory and glossary resources but does not create, modify, or delete any persistent data. The output is a transformed version of the input text, not a side effect on system state. Translation is fundamentally a data retrieval and processing operation, placing it squarely in the Read category.
From the tool's definition Tool description states it 'Translate[s] text between languages' with support for language detection and context-aware translations. The verb 'translate' is a query/transformation operation that retrieves or processes data without modifying persistent state.
Attacks that exploit this kind of access
Translate text between languages using Lara Translate. Supports language detection, context-aware translations, translation memories, and glossaries. It is categorised as a Read tool in the Lara MCP Server, which means it retrieves data without modifying state.
Register the Lara MCP server in PolicyLayer and add a rule for translate: 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 Lara. Nothing to install.
translate 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 translate 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 translate. 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.
translate is provided by the Lara MCP server (@translated/lara-mcp). 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 →