AI agents use update_glossary 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 modifies glossary metadata (the name) in a reversible manner. It does not execute code, delete data irreversibly, or move money. The change can be undone by updating the name again, making it a Write rather than Destructive action. The blast radius is minimal since renaming a glossary does not affect data integrity or dependent systems in a catastrophic way.
From the tool's definition Tool description states 'Updates the name of a glossary' — a modification operation that changes metadata reversibly.
Attacks that exploit this kind of access
Updates the name of a glossary 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 update_glossary: 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.
update_glossary 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 update_glossary 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 update_glossary. 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.
update_glossary 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 →