Alternative bulk translation: translate multiple English texts to all project locales using backend AI (Gemini). Prefer agent-local translation for batches under 100 keys (better quality with context awareness). Use this for large bulk operations (100+ keys) where speed matters more than per-key ...
AI agents use bulk_ai_translate 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 |
|---|---|---|---|
entries | array | Yes | Array of entries to translate |
projectSlug | string | Yes | Project slug (required for locale resolution and usage tracking) |
targetLocales | array | — | Optional list of locale codes. When omitted, translates to all non-default project locales. |
Parameters from the server's own tool schema.
This tool writes AI-generated translations for multiple keys across all project locales. It creates/modifies translation data at scale (up to 200 entries across all locales), making it a Write operation with high severity due to the broad blast radius — a misuse could overwrite hundreds of translations across an entire localization project with incorrect content.
From the tool's definition translate multiple English texts to all project locales using backend AI... bulk operations (100+ keys)... Max 200 entries
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Alternative bulk translation: translate multiple English texts to all project locales using backend AI (Gemini). Prefer agent-local translation for batches under 100 keys (better quality with context awareness). Use this for large bulk operations (100+ keys) where speed matters more than per-key attention. Processes in batches of 10 keys per AI call. Max 200 entries. 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_ai_translate accepts 3 parameters: entries, projectSlug, targetLocales. Required: entries, 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_ai_translate: 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_ai_translate 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_ai_translate 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_ai_translate. 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_ai_translate 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 →