Create a translation memory with a custom name in your Lara Translate account. Translation memories store pairs of source and target text segments (translation units) for reuse in future translations.
AI agents use create_memory 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 performs a create operation that adds a new data object (translation memory) to the user's account. While reversible (can be deleted via delete_glossary or similar), it modifies the account state by introducing a new persistent resource. This is a Write category action—it creates structured data without executing arbitrary code or triggering external operations.
From the tool's definition Tool creates a translation memory with a custom name in the Lara Translate account. The description explicitly states it will 'create' a new resource that 'stores pairs of source and target text segments' for reuse.
Attacks that exploit this kind of access
Create a translation memory with a custom name in your Lara Translate account. Translation memories store pairs of source and target text segments (translation units) for reuse in future translations. 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 create_memory: 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.
create_memory 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 create_memory 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 create_memory. 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.
create_memory 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 →