Imports a TMX file into a translation memory. This is an async operation that returns an import job object containing an import_id. Poll with check_import_status using the returned import_id until the import is complete.
AI agents use import_tmx 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 accepts external TMX (Translation Memory eXchange) file data and writes it into a translation memory store. While the import operation is asynchronous and does not immediately delete or overwrite existing entries, it does persistently modify the state of the translation memory by adding translation records.
From the tool's definition Tool description states 'Imports a TMX file into a translation memory' — this creates or modifies data in a translation memory system.
Attacks that exploit this kind of access
Imports a TMX file into a translation memory. This is an async operation that returns an import job object containing an import_id. Poll with check_import_status using the returned import_id until the import is complete. 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 import_tmx: 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.
import_tmx 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 import_tmx 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 import_tmx. 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.
import_tmx 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 →