AI agents use strings_update_job_locale 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.
The tool creates or modifies data reversibly by updating job locale settings. It does not delete data (would be Destructive), execute arbitrary code (would be Execute), or move money (would be Financial). The 'medium' severity reflects that misconfiguration could disrupt localization workflows, but the impact is reversible and scoped to a single job locale assignment.
From the tool's definition Tool name contains 'update' and description states 'Update a target locale for a job' — this modifies job configuration in the Phrase localization system.
Attacks that exploit this kind of access
Update a target locale for a job in a Phrase Strings project. 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_job_locale: 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_job_locale 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_job_locale 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_job_locale. 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_job_locale 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 →