Rename a translation key in a namespace. Preserves all translation values and sandbox values — only the key name changes. The new key name must not already exist in the namespace. This is a sandbox operation — the rename takes effect in sandbox and is reflected in diffs.
AI agents use rename_key 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 |
|---|---|---|---|
newKey | string | Yes | New key name |
oldKey | string | Yes | Current key name to rename |
namespace | string | Yes | Namespace slug |
projectSlug | string | Yes | Project slug |
Parameters from the server's own tool schema.
This tool creates or modifies data in a reversible manner (renaming keys). It is not destructive because the operation can be undone and all translation values are preserved. It is not Read-only since it actively changes the state of translation keys. It falls into Write category as it modifies localization metadata.
From the tool's definition Tool description states it will 'Rename a translation key in a namespace' and 'the rename takes effect in sandbox' — this modifies existing data (the key identifier) reversibly within the localization system.
Attacks that exploit this kind of access
Rename a translation key in a namespace. Preserves all translation values and sandbox values — only the key name changes. The new key name must not already exist in the namespace. This is a sandbox operation — the rename takes effect in sandbox and is reflected in diffs. 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_key accepts 4 parameters: newKey, oldKey, namespace, projectSlug. Required: newKey, oldKey, 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 rename_key: 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_key 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_key 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_key. 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_key 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 →