Before writing to a project for the first time in a session, call assess_integration_state to understand client URL patterns and integration state. Bulk upsert multiple keys for a SINGLE locale in the sandbox. Designed for the new-locale fill workflow: after adding a locale, use this to fill many...
AI agents use bulk_set_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 |
|---|---|---|---|
dryRun | boolean | — | If true, preview what would be written without actually writing |
locale | string | Yes | The single locale to write values for (e.g. 'nb-NO'). Must match the project's locale codes exactly. |
entries | array | Yes | Array of { key, value, context? } pairs to upsert for the given locale. |
namespace | string | Yes | Namespace slug — must already exist |
projectSlug | string | Yes | Project slug |
Parameters from the server's own tool schema.
This tool creates or modifies translation entries (upsert operation) for a locale. It is reversible (can be undone by updating or deleting entries), does not execute arbitrary code, and does not delete data permanently. It operates within a sandbox environment on a localization system.
From the tool's definition "Bulk upsert multiple keys for a SINGLE locale" and "only the specified locale is written" indicate reversible creation or modification of translation data.
Attacks that exploit this kind of access
Before writing to a project for the first time in a session, call assess_integration_state to understand client URL patterns and integration state. Bulk upsert multiple keys for a SINGLE locale in the sandbox. Designed for the new-locale fill workflow: after adding a locale, use this to fill many keys at once for keys that already exist. Only the specified locale is written — all other locales on each key remain untouched. NOTE: Use this tool for keys that already exist in the namespace. For brand-new keys use set_translation (which requires source locale on create). Use list_translations with missingLocale to get the list of keys to fill. For multi-locale bulk import use bulk_import instead. 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.
bulk_set_locale accepts 5 parameters: dryRun, locale, entries, namespace, projectSlug. Required: locale, entries, namespace, 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 bulk_set_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.
bulk_set_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 bulk_set_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 bulk_set_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.
bulk_set_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 →