// SCAN REPORT

Lara

22 tools. 12 can modify or destroy data without limits.

4 destructive tools with no built-in limits. Policy required.

Last updated: 27 Jun 2026

12 can modify or destroy data

10 read-only

22 tools total

Community server · catalogue entry verified 27/06/2026

How to control Lara ↓

TOOL MAP

What Lara exposes to your agents

Read (10) Write / Execute (8) Destructive / Financial (4)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Lara tools

Destructive · High delete_glossary Deletion of a glossary is a destructive action that cannot be undone and eliminates data. Destructive · High delete_glossary_entry This tool permanently removes glossary entries without the ability to undo the operation. Destructive · High delete_memory This tool permanently removes data (translation memory) from a user's account with no ability to undo the action. Destructive · High delete_translation This tool permanently removes translations from a user's translation memory.

12 of Lara's 22 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Lara

PolicyLayer is an MCP gateway — it sits between your AI agents and Lara, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations

{
  "delete_glossary": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "add_glossary_entry": {
    "limits": [
      {
        "counter": "add_glossary_entry_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "check_glossary_import_status": {
    "limits": [
      {
        "counter": "check_glossary_import_status_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Lara — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON LARA →

Instant setup, no code required.

FULL CATALOGUE

All 22 Lara tools

DESTRUCTIVE 4 tools

Destructive delete_glossary Deletes a glossary from your Lara Translate account. Destructive delete_glossary_entry Deletes an entry from a glossary in your Lara Translate account. Use term for monodirectional glossaries or gu Destructive delete_memory Deletes a translation memory from your Lara Translate account. Destructive delete_translation Deletes a translation from a translation memory in your Lara Translate account.

WRITE 8 tools

Write add_glossary_entry Adds or replaces an entry in a glossary in your Lara Translate account. Supports both monodirectional and mult Write add_translation Adds a translation to a translation memory in your Lara Translate account. Write create_glossary Create a glossary with a custom name in your Lara Translate account. Glossaries enforce specific terminology d Write create_memory Create a translation memory with a custom name in your Lara Translate account. Translation memories store pair Write import_glossary_csv Imports a CSV file into a glossary. Supports unidirectional and multidirectional formats. This is an async ope Write import_tmx Imports a TMX file into a translation memory. This is an async operation that returns an import job object con Write update_glossary Updates the name of a glossary in your Lara Translate account. Write update_memory Updates a translation memory in your Lara Translate account.

READ 10 tools

Read check_glossary_import_status Checks the status of a glossary CSV import job started by import_glossary_csv. Poll this tool with the import_ Read check_import_status Checks the status of a TMX import job started by import_tmx. Poll this tool with the import_id returned from i Read detect_language Detects the language of the provided text. Returns the detected language, content type, and a list of predicti Read export_glossary Exports a glossary as CSV from your Lara Translate account. Supports unidirectional and multidirectional forma Read get_glossary Retrieves a specific glossary by ID from your Lara Translate account. Returns null if the glossary is not foun Read get_glossary_counts Retrieves the term and language counts for a glossary in your Lara Translate account. Read list_glossaries Lists all glossaries in your Lara Translate account. Glossaries are collections of terms with their translatio Read list_languages Lists all supported languages in your Lara Translate account. Read list_memories Lists all translation memories in your Lara Translate account. Read translate Translate text between languages using Lara Translate. Supports language detection, context-aware translations

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about Lara

Can an AI agent delete data through the Lara MCP server? +

Yes. The Lara server exposes 4 destructive tools including delete_glossary, delete_glossary_entry, delete_memory. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Lara? +

The Lara server has 8 write tools including add_glossary_entry, add_translation, create_glossary. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Lara.

How many tools does the Lara MCP server expose? +

22 tools across 3 categories: Destructive, Read, Write. 10 are read-only. 12 can modify, create, or delete data.

How do I enforce a policy on Lara? +

Register the Lara MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Lara tool call.

Deterministic rules across all 22 Lara tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON LARA →

Instant setup, no code required.

22 Lara tools catalogued and risk-classified — across an index of 43,000+ MCP servers.