Get full details of a translation project: namespaces, locales, and sandbox state. ALWAYS call this before writing to a project — you need the exact locale codes and namespace list. Locale codes returned here are the only valid codes for set_translation, bulk_import, bulk_set_locale, and create_l...
AI agents call get_project_details 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 tool retrieves and queries project configuration data without modifying, creating, deleting, or executing any operations. It has no side effects and poses minimal risk if invoked by an AI agent—the worst outcome is obtaining information about project structure. It belongs in the Read category with low severity.
From the tool's definition Tool description states 'Get full details' and is clearly informational—it retrieves project metadata (namespaces, locales, sandbox state) with no side effects.
Attacks that exploit this kind of access
Get full details of a translation project: namespaces, locales, and sandbox state. ALWAYS call this before writing to a project — you need the exact locale codes and namespace list. Locale codes returned here are the only valid codes for set_translation, bulk_import, bulk_set_locale, and create_locale. Use the namespace list to decide whether to reuse an existing namespace or justify creating a new one. Client apps fetch translations via REST GET /translations/{slug}/{namespace}/{locale} — MCP is for AI agents only. It is categorised as a Read tool in the Localization MCP Server, which means it retrieves data without modifying state.
get_project_details 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 get_project_details: 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_project_details 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_project_details 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_project_details. 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_project_details 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 →