AI agents use strings_update_glossary 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.
This tool creates or modifies data reversibly within Phrase's glossary/term base system. Updates can typically be reverted or corrected, making it a Write operation rather than Destructive. The blast radius is medium because incorrect glossary updates could affect translation quality across projects, but the operation is not irreversible and does not involve financial transactions or code execution.
From the tool's definition Tool name 'strings_update_glossary' with description 'Update a term base (previously: glossary) in Phrase Strings' indicates modification of existing data (glossaries/term bases) in a localization system.
Attacks that exploit this kind of access
Update a term base (previously: glossary) in Phrase Strings. 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.
Register the Phrase MCP server in PolicyLayer and add a rule for strings_update_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 Phrase. Nothing to install.
strings_update_glossary is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the strings_update_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.
Set action: deny in the PolicyLayer policy for strings_update_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.
strings_update_glossary 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.
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 →