List all namespaces in a translation project. Returns namespace slugs and average quality scores. Use this to see available namespaces before calling list_translations or bulk operations.
AI agents call list_namespaces 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 |
|---|---|---|---|
projectSlug | string | Yes | Project slug (e.g. 'my-app') |
Parameters from the server's own tool schema.
This is a straightforward read-only operation that queries and returns information about available namespaces. It has no capability to modify, delete, or execute operations—it only retrieves metadata. The severity is low as misuse would only expose existing namespace information without enabling harmful actions on the localization system itself.
From the tool's definition Tool name is 'list_namespaces' and description states 'List all namespaces in a translation project. Returns namespace slugs and average quality scores.' The verb 'List' combined with 'Returns' indicates pure data retrieval with no side effects.
Attacks that exploit this kind of access
List all namespaces in a translation project. Returns namespace slugs and average quality scores. Use this to see available namespaces before calling list_translations or bulk operations. It is categorised as a Read tool in the Localization MCP Server, which means it retrieves data without modifying state.
list_namespaces accepts 1 parameter: projectSlug. 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 list_namespaces: 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.
list_namespaces 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 list_namespaces 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 list_namespaces. 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.
list_namespaces 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 →