strings_update_glossary_term_translation

WHAT IT DOES

What strings_update_glossary_term_translation does on Phrase

AI agents use strings_update_glossary_term_translation to create or update resources in Phrase — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Phrase environment.

WHY IT NEEDS A POLICY

Why strings_update_glossary_term_translation needs a policy

The tool creates or modifies translation data within a glossary/term base. This is a reversible change (translations can be updated again or reverted), making it a Write operation rather than Destructive.

From the tool's definition Tool name contains 'update' and description states 'Update a translation for a term in a term base'. This modifies existing localization data reversibly.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

strings_update_glossary_term_translation Rate-limited

strings_update_glossary_term_translation 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": {
    "strings_update_glossary_term_translation": {
      "limits": [
        {
          "counter": "strings_update_glossary_term_translation_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 Phrase, so you can run agents against it safely.

FAQ

Questions about strings_update_glossary_term_translation

What does the strings_update_glossary_term_translation tool do? +

Update a translation for a term in a term base (previously: glossary). It is categorised as a Write tool in the Phrase MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on strings_update_glossary_term_translation? +

Register the Phrase MCP server in PolicyLayer and add a rule for strings_update_glossary_term_translation: 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 Phrase. Nothing to install.

What risk level is strings_update_glossary_term_translation? +

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

Can I rate-limit strings_update_glossary_term_translation? +

Yes. Add a rate_limit block to the strings_update_glossary_term_translation 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 strings_update_glossary_term_translation completely? +

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

strings_update_glossary_term_translation is provided by the Phrase MCP server (phrase-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

strings_update_glossary_term_translation is one line of Phrase's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →