Deletes an entry from a glossary in your Lara Translate account. Use term for monodirectional glossaries or guid for multidirectional glossaries.
AI agents call delete_glossary_entry to permanently remove resources in Lara — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes glossary entries without the ability to undo the operation. While the blast radius is limited to glossary data (not critical business operations), deletion operations that cannot be reversed fall squarely into the Destructive category, which supersedes Write.
From the tool's definition Tool explicitly performs 'Deletes an entry from a glossary' — the action is irreversible deletion of data.
Attacks that exploit this kind of access
Deletes an entry from a glossary in your Lara Translate account. Use term for monodirectional glossaries or guid for multidirectional glossaries. It is categorised as a Destructive tool in the Lara MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Lara MCP server in PolicyLayer and add a rule for delete_glossary_entry: 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.
delete_glossary_entry is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_glossary_entry 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 delete_glossary_entry. 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.
delete_glossary_entry 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 →