Delete a namespace from a project. This cascades to ALL keys and values in the namespace. This is a destructive and irreversible operation.
AI agents call delete_namespace 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 |
|---|---|---|---|
confirmed | boolean | — | Must be true to execute. Without confirmation, returns a warning. |
namespace | string | Yes | Namespace slug to delete |
projectSlug | string | Yes | Project slug |
Parameters from the server's own tool schema.
This tool permanently removes an entire namespace and all associated translation keys and values without possibility of recovery. The description unambiguously confirms irreversibility and cascading scope, making it Destructive rather than merely Write.
From the tool's definition 'Delete a namespace from a project. This cascades to ALL keys and values in the namespace. This is a destructive and irreversible operation.' — explicitly states destructive, irreversible, and cascading deletion of all contained data.
Attacks that exploit this kind of access
Delete a namespace from a project. This cascades to ALL keys and values in the namespace. This is a destructive and irreversible operation. 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_namespace accepts 3 parameters: confirmed, 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 delete_namespace: 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_namespace 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_namespace 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_namespace. 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_namespace 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 →