add_glossary_entry · Lara MCP: Risk & Policy

WHAT IT DOES

What add_glossary_entry does on Lara

AI agents use add_glossary_entry 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.

WHY IT NEEDS A POLICY

Why add_glossary_entry needs a policy

This tool creates or modifies glossary entries reversibly. While it doesn't delete data, 'replaces' indicates overwriting capability, making it a Write operation. The blast radius is medium because corrupted glossary entries could affect translation quality downstream, but the operation is reversible (entries can be corrected or re-added).

From the tool's definition Tool description states it 'Adds or replaces an entry in a glossary', which are create and update operations on glossary data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_glossary_entry Rate-limited

add_glossary_entry stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "add_glossary_entry": {
      "limits": [
        {
          "counter": "add_glossary_entry_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Lara, so you can run agents against it safely.

FAQ

Questions about add_glossary_entry

What does the add_glossary_entry tool do? +

Adds or replaces an entry in a glossary in your Lara Translate account. Supports both monodirectional and multidirectional glossaries. 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.

How do I enforce a policy on add_glossary_entry? +

Register the Lara MCP server in PolicyLayer and add a rule for add_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.

What risk level is add_glossary_entry? +

add_glossary_entry is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit add_glossary_entry? +

Yes. Add a rate_limit block to the add_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.

How do I block add_glossary_entry completely? +

Set action: deny in the PolicyLayer policy for add_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.

What MCP server provides add_glossary_entry? +

add_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.