Delete one or more translation keys from the sandbox (soft delete). Keys remain in production until you promote the sandbox.
AI agents call delete_translation 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 |
|---|---|---|---|
keys | array | Yes | Keys to delete (1–500) |
namespace | string | Yes | Namespace slug |
projectSlug | string | Yes | Project slug |
Parameters from the server's own tool schema.
Although the deletion is scoped to a sandbox and marked as 'soft delete', the tool permanently removes translation data that cannot be recovered without external restoration. The rationale for Destructive rather than Write: the operation is deletion-based and irreversible within the sandbox context.
From the tool's definition delete_translation with description 'Delete one or more translation keys from the sandbox (soft delete)'. The tool performs irreversible deletion of translation entries, even though it operates on a sandbox rather than direct production.
Attacks that exploit this kind of access
Delete one or more translation keys from the sandbox (soft delete). Keys remain in production until you promote the sandbox. 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_translation accepts 3 parameters: keys, namespace, projectSlug. Required: keys, 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 delete_translation: 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_translation 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_translation 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_translation. 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_translation 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 →