Export all translation keys for a namespace as a flat JSON map, per locale. Use this to see the full content of a namespace, compare before/after migration, or get the data needed for bulk_import.
AI agents call export_namespace 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 export from (default: production) |
locale | string | — | Export only this locale. If omitted, exports all locales. |
namespace | string | Yes | Namespace slug |
projectSlug | string | Yes | Project slug |
Parameters from the server's own tool schema.
The tool reads and exports translation data without modifying or deleting anything. It retrieves existing translation keys as a JSON map, making it a pure read/query operation with minimal blast radius.
From the tool's definition Export all translation keys for a namespace as a flat JSON map, per locale. Use this to see the full content of a namespace, compare before/after migration, or get the data needed for bulk_import.
Attacks that exploit this kind of access
Export all translation keys for a namespace as a flat JSON map, per locale. Use this to see the full content of a namespace, compare before/after migration, or get the data needed for bulk_import. It is categorised as a Read tool in the Localization MCP Server, which means it retrieves data without modifying state.
export_namespace accepts 4 parameters: env, locale, 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 export_namespace: 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.
export_namespace 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 export_namespace 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 export_namespace. 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.
export_namespace 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 →