create_glossary · Lara MCP: Risk & Policy

WHAT IT DOES

What create_glossary does on Lara

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

WHY IT NEEDS A POLICY

Why create_glossary needs a policy

This tool creates new data structures (glossaries) that persist in the user's account and can be used to influence translation behavior. It is reversible (glossaries can be deleted via delete_glossary), making it a Write operation rather than Destructive.

From the tool's definition Tool description states it will 'Create a glossary' in the user's Lara Translate account, which involves creating new data (a glossary resource with a custom name).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_glossary Rate-limited

create_glossary 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": {
    "create_glossary": {
      "limits": [
        {
          "counter": "create_glossary_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 create_glossary

What does the create_glossary tool do? +

Create a glossary with a custom name in your Lara Translate account. Glossaries enforce specific terminology during translation. 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 create_glossary? +

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

What risk level is create_glossary? +

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

Can I rate-limit create_glossary? +

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

How do I block create_glossary completely? +

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

What MCP server provides create_glossary? +

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