Get the diff between sandbox and production for a project. Returns paginated results (default: 50 per page). Shows added, changed, and deleted entries.
AI agents call get_translation_diff 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 |
|---|---|---|---|
page | integer | — | Page number (default: 1) |
limit | integer | — | Items per page (default: 50, max: 200) |
locale | string | — | Filter diff to a specific locale (optional) |
namespace | string | — | Filter diff to a specific namespace (optional) |
projectSlug | string | Yes | Project slug |
statusFilter | string | — | Filter by change type (default: all) |
Parameters from the server's own tool schema.
This tool retrieves and displays differences between two states (sandbox vs production translations) but does not modify, delete, or execute any operations. It is a pure query/comparison function with no side effects. The read-only nature and absence of any write, delete, or execution capabilities place it firmly in the Read category with low severity risk.
From the tool's definition Tool description states it 'Get[s] the diff between sandbox and production' and 'Returns paginated results' and 'Shows added, changed, and deleted entries.' The verb 'Get' and the retrieval-only nature (comparing existing states without modification) indicate…
Attacks that exploit this kind of access
Get the diff between sandbox and production for a project. Returns paginated results (default: 50 per page). Shows added, changed, and deleted entries. It is categorised as a Read tool in the Localization MCP Server, which means it retrieves data without modifying state.
get_translation_diff accepts 6 parameters: page, limit, locale, namespace, projectSlug, statusFilter. 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 get_translation_diff: 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.
get_translation_diff 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 get_translation_diff 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 get_translation_diff. 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.
get_translation_diff 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 →