Remove a locale from a project. This deletes ALL translation values for that locale across all namespaces. This is a destructive operation — use with caution. The default locale cannot be deleted.
AI agents call delete_locale to permanently remove resources in Localization — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
code | string | Yes | Locale code to delete (e.g. 'nb-NO') |
confirmed | boolean | — | Must be true to execute. Without confirmation, returns a warning. |
projectSlug | string | Yes | Project slug |
Parameters from the server's own tool schema.
The tool irreversibly deletes translation data at scale (all values for an entire locale across all namespaces). This cannot be undone and represents a destructive operation as confirmed by the description itself.
From the tool's definition Tool description explicitly states: 'Remove a locale from a project. This deletes ALL translation values for that locale across all namespaces. This is a destructive operation — use with caution.'
Risk signalsAccepts freeform code/query input (code)
Attacks that exploit this kind of access
Remove a locale from a project. This deletes ALL translation values for that locale across all namespaces. This is a destructive operation — use with caution. The default locale cannot be deleted. It is categorised as a Destructive tool in the Localization MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
delete_locale accepts 3 parameters: code, confirmed, projectSlug. Required: code, 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 delete_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.
delete_locale is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_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 delete_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.
delete_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 →