Update locale settings — currently supports setting locale aliases. Aliases allow a single locale to serve multiple codes (e.g. 'nb-NO' can have alias 'no'). When a client requests translations for an alias code, the server returns the parent locale's translations.
AI agents use update_locale to create or update resources in Localization — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Localization environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
code | string | Yes | Locale code to update (e.g. 'nb-NO') |
aliases | array | Yes | List of alias codes for this locale (e.g. ['no', 'nb'] for nb-NO). Pass empty array to clear aliases. |
projectSlug | string | Yes | Project slug |
Parameters from the server's own tool schema.
This tool modifies localization configuration (locale aliases) rather than translation content itself. While it affects how the system behaves, the changes are reversible—aliases can be removed or updated. This qualifies as Write (modifies data reversibly) rather than Execute or Destructive.
From the tool's definition Tool description states 'Update locale settings' and 'allow[s] a single locale to serve multiple codes', indicating modification of configuration data. The mechanism creates aliases that affect translation routing, which is a reversible configuration change.
Risk signalsAccepts freeform code/query input (code)
Attacks that exploit this kind of access
Update locale settings — currently supports setting locale aliases. Aliases allow a single locale to serve multiple codes (e.g. 'nb-NO' can have alias 'no'). When a client requests translations for an alias code, the server returns the parent locale's translations. It is categorised as a Write tool in the Localization MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
update_locale accepts 3 parameters: code, aliases, projectSlug. Required: code, aliases, projectSlug. The full parameter table on this page comes from the server's own tool schema.
Register the Localization MCP server in PolicyLayer and add a rule for update_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 Localization. Nothing to install.
update_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 update_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 update_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.
update_locale is provided by the Localization MCP server (localization-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 →