Show a full diff of what sandbox changes would replace production if promoted. Read-only — does NOT push anything. Pushing to production must be done manually via the Admin UI.
AI agents call preview_push_to_production to retrieve information from Localization without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
projectSlug | string | Yes | Project slug |
Parameters from the server's own tool schema.
The tool only computes and displays a diff between sandbox and production states. It explicitly states it is read-only and performs no actual push or modification. No data is created, modified, or deleted.
From the tool's definition "Show a full diff of what sandbox changes would replace production if promoted. Read-only — does NOT push anything."
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
Show a full diff of what sandbox changes would replace production if promoted. Read-only — does NOT push anything. Pushing to production must be done manually via the Admin UI. It is categorised as a Read tool in the Localization MCP Server, which means it retrieves data without modifying state.
preview_push_to_production accepts 1 parameter: projectSlug. Required: 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 preview_push_to_production: 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.
preview_push_to_production is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the preview_push_to_production 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 preview_push_to_production. 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.
preview_push_to_production 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 →