Compare a local translation map against a namespace on the server. Returns: keys only in local (need importing), keys only on server (not in local), keys with different values (conflicts), and a count of matching keys. Run this BEFORE bulk_import to avoid re-importing keys that already exist with...
AI agents call compare_local_vs_server 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 |
|---|---|---|---|
env | string | — | Which environment to compare against (default: sandbox) |
filePath | string | — | Absolute path to a JSON file on disk. Format: { "locale": { "key": "value" } } |
namespace | string | Yes | Namespace slug |
projectSlug | string | Yes | Project slug |
translations | object | — | Inline locale → key → value map to compare against server |
Parameters from the server's own tool schema.
This tool only reads and compares data between a local map and server namespace, returning a diff report. It has no side effects — it explicitly recommends running this BEFORE bulk_import, confirming it does not modify anything itself.
From the tool's definition Compare a local translation map against a namespace on the server. Returns: keys only in local, keys only on server, keys with different values, and a count of matching keys.
Risk signalsAccepts file system path (filePath)
Attacks that exploit this kind of access
Compare a local translation map against a namespace on the server. Returns: keys only in local (need importing), keys only on server (not in local), keys with different values (conflicts), and a count of matching keys. Run this BEFORE bulk_import to avoid re-importing keys that already exist with the same values. Accepts either an inline translations map or a filePath to a JSON file on disk. It is categorised as a Read tool in the Localization MCP Server, which means it retrieves data without modifying state.
compare_local_vs_server accepts 5 parameters: env, filePath, namespace, projectSlug, translations. Required: 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 compare_local_vs_server: 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.
compare_local_vs_server 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 compare_local_vs_server 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 compare_local_vs_server. 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.
compare_local_vs_server 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 →