AI agents call export_glossary 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.
The tool retrieves/exports data (a glossary in CSV format) without modifying, deleting, or creating anything. This is a read-only operation with minimal blast radius.
From the tool's definition Exports a glossary as CSV from your Lara Translate account
Attacks that exploit this kind of access
Exports a glossary as CSV from your Lara Translate account. Supports unidirectional and multidirectional formats. 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 export_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.
export_glossary 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 export_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 export_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.
export_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 →