Delete sandbox translations and trigger re-translation. Scope: namespace (no params), single locale ({ locale }), multiple locales ({ locales: ["de","fr"] }), or single key+locale ({ key, locale }). The auto-translate worker will re-populate deleted values asynchronously. Use when you need to reg...
AI agents call reset_namespace_translations 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 |
|---|---|---|---|
key | string | — | Key name — requires locale; omit to retranslate the whole namespace/locale scope |
locale | string | — | Single locale code — omit to retranslate all non-default locales. Use "locales" for multiple. |
locales | array | — | Array of locale codes to retranslate (e.g. ["de","fr"]). Alternative to single "locale" param. |
namespace | string | Yes | Namespace slug |
projectSlug | string | Yes | Project slug |
Parameters from the server's own tool schema.
This tool deletes data that cannot be immediately recovered. While the description mentions 'auto-translate worker will re-populate deleted values asynchronously', the primary action is deletion of existing translations. This is irreversible in the immediate sense and represents data loss.
From the tool's definition Tool description explicitly states 'Delete sandbox translations' and 'deleted values'. The tool irreversibly removes translation data across configurable scopes (namespace, locale, key+locale), with only asynchronous regeneration as recovery.
Attacks that exploit this kind of access
Delete sandbox translations and trigger re-translation. Scope: namespace (no params), single locale ({ locale }), multiple locales ({ locales: ["de","fr"] }), or single key+locale ({ key, locale }). The auto-translate worker will re-populate deleted values asynchronously. Use when you need to regenerate translations (e.g. after updating AI config or locale skill). Only non-default locales are affected — source/default locale values are preserved. 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.
reset_namespace_translations accepts 5 parameters: key, locale, locales, namespace, projectSlug. Required: 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 reset_namespace_translations: 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.
reset_namespace_translations 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 reset_namespace_translations 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 reset_namespace_translations. 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.
reset_namespace_translations 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 →