Read-only preflight analysis of a planned batch of translation keys. Checks: (1) duplicate keys within the submitted batch, (2) conflicts with existing keys in the namespace (same key, different value), (3) source text overlap — signals a potential reuse opportunity, but NOT a hard rule (the same...
AI agents call analyze_entries 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 |
|---|---|---|---|
entries | array | Yes | Array of { key, text, context? } entries to analyze |
namespace | string | Yes | Namespace slug |
projectSlug | string | Yes | Project slug |
sourceLocale | string | — | Source locale code. Defaults to project default locale. |
Parameters from the server's own tool schema.
The tool performs analysis and validation of translation entries before they are submitted for processing. It retrieves and examines data (checks for duplicates, conflicts, and overlaps) but takes no action that creates, modifies, deletes, or executes external operations. This is a pure read operation characteristic of data validation and querying tools.
From the tool's definition Tool is described as 'Read-only preflight analysis' that 'Checks: (1) duplicate keys within the submitted batch, (2) conflicts with existing keys in the namespace, (3) source text overlap' and explicitly states 'Does NOT create or modify anything.' These are…
Attacks that exploit this kind of access
Read-only preflight analysis of a planned batch of translation keys. Checks: (1) duplicate keys within the submitted batch, (2) conflicts with existing keys in the namespace (same key, different value), (3) source text overlap — signals a potential reuse opportunity, but NOT a hard rule (the same word can have different translations in different contexts). Call BEFORE bulk_translate_and_save or set_translation when adding many new keys. Does NOT create or modify anything. Before submitting entries, follow key naming rules: short context-agnostic names consistent with existing project style; no location suffixes (e.g. submit_button not page_header_submit_button). It is categorised as a Read tool in the Localization MCP Server, which means it retrieves data without modifying state.
analyze_entries accepts 4 parameters: entries, namespace, projectSlug, sourceLocale. Required: entries, 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 analyze_entries: 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.
analyze_entries 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 analyze_entries 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 analyze_entries. 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.
analyze_entries 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 →