Rename an existing namespace in a project. All keys and values are preserved — only the slug changes. The new slug must not already exist in the project.
AI agents use rename_namespace 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 |
|---|---|---|---|
newSlug | string | Yes | New namespace slug |
currentSlug | string | Yes | Current namespace slug |
projectSlug | string | Yes | Project slug |
Parameters from the server's own tool schema.
This tool modifies project data by changing a namespace identifier/slug, which is a structural update to the localization system. It is reversible (the old name could be restored by renaming back), affecting configuration rather than deletion. However, the modification could have downstream impacts on systems that reference the old namespace name, making it medium severity.
From the tool's definition Tool description states: 'Rename an existing namespace in a project. All keys and values are preserved — only the slug changes.' This modifies metadata (the namespace slug) in a reversible manner.
Attacks that exploit this kind of access
Rename an existing namespace in a project. All keys and values are preserved — only the slug changes. The new slug must not already exist in the project. 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.
rename_namespace accepts 3 parameters: newSlug, currentSlug, projectSlug. Required: newSlug, currentSlug, 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 rename_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.
rename_namespace 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 rename_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 rename_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.
rename_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 →