Show per-locale fill statistics for a namespace. Returns: total keys, how many have a non-empty value for each locale, and coverage percentage. Also lists the first 10 keys missing each locale. Use this after adding a new locale to understand the fill gap before starting bulk_set_locale.
AI agents call get_namespace_coverage 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 analyze (default: sandbox) |
namespace | string | Yes | Namespace slug |
projectSlug | string | Yes | Project slug |
Parameters from the server's own tool schema.
This tool queries and reports statistics about localization namespace coverage. It performs no writes, deletes, executions, or financial operations. The recommendation to use it 'before starting bulk_set_locale' confirms it is a read-only diagnostic tool meant to inform subsequent actions, not perform them.
From the tool's definition Tool description states it 'Show[s] per-locale fill statistics' and 'Returns: total keys, how many have a non-empty value for each locale, and coverage percentage.' The verb 'Show' and 'Returns' indicate pure data retrieval with no modification or side…
Attacks that exploit this kind of access
Show per-locale fill statistics for a namespace. Returns: total keys, how many have a non-empty value for each locale, and coverage percentage. Also lists the first 10 keys missing each locale. Use this after adding a new locale to understand the fill gap before starting bulk_set_locale. It is categorised as a Read tool in the Localization MCP Server, which means it retrieves data without modifying state.
get_namespace_coverage accepts 3 parameters: env, namespace, projectSlug. 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 get_namespace_coverage: 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_namespace_coverage 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_namespace_coverage 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_namespace_coverage. 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_namespace_coverage 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 →