AI agents use add_translation to create or update resources in Lara — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Lara environment.
This tool creates or modifies data in a translation memory system. Adding translations is a reversible operation—entries can be deleted or updated later. The blast radius is medium because a compromised AI agent could pollute translation memories with incorrect entries, causing downstream translation quality issues, but the operation is not irreversible and does not involve financial transactions or code execution.
From the tool's definition Tool description states it 'Adds a translation' which is a create/modify operation. The sibling tools include 'delete_translation' and 'delete_glossary_entry', establishing a pattern where write operations are paired with destructive counterparts.
Attacks that exploit this kind of access
Adds a translation to a translation memory in your Lara Translate account. It is categorised as a Write tool in the Lara MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Lara MCP server in PolicyLayer and add a rule for add_translation: 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.
add_translation is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the add_translation 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 add_translation. 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.
add_translation 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 →