Revert a specific key in sandbox back to its production value. Useful when you want to undo a sandbox edit for one key without resetting the entire sandbox. If the key was added in sandbox (not in production), this effectively removes it.
AI agents use revert_sandbox_entry 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 |
|---|---|---|---|
key | string | Yes | Translation key to revert |
namespace | string | Yes | Namespace slug |
projectSlug | string | Yes | Project slug |
Parameters from the server's own tool schema.
This tool modifies sandbox translation data by reverting entries to production values or removing sandbox-only keys. The operation is reversible (the original sandbox state could theoretically be re-edited), distinguishing it from Destructive. It does not delete production data, only sandbox state.
From the tool's definition Tool description states it 'Revert[s] a specific key in sandbox back to its production value' and 'effectively removes it' if the key was added in sandbox. These are reversible modifications to sandbox state.
Attacks that exploit this kind of access
Revert a specific key in sandbox back to its production value. Useful when you want to undo a sandbox edit for one key without resetting the entire sandbox. If the key was added in sandbox (not in production), this effectively removes it. 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.
revert_sandbox_entry accepts 3 parameters: key, namespace, projectSlug. Required: key, 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 revert_sandbox_entry: 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.
revert_sandbox_entry 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 revert_sandbox_entry 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 revert_sandbox_entry. 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.
revert_sandbox_entry 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 →