Analyze the sandbox diff for potential issues: empty values, locales missing translations that others have, and keys only partially translated.
AI agents call validate_translations 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 |
|---|---|---|---|
namespace | string | — | Limit validation to a specific namespace (optional) |
projectSlug | string | Yes | Project slug |
Parameters from the server's own tool schema.
validate_translations performs analysis and reporting on translation state. The word 'analyze' combined with checking for empty values, missing locales, and partial translations indicates a read-only audit function. No data is modified, created, or destroyed. Severity is low because misuse would only surface incorrect information, not corrupt the system or cause side effects.
From the tool's definition Tool description states 'Analyze the sandbox diff' for checking 'potential issues' — this is a validation/inspection operation with no modification of data.
Attacks that exploit this kind of access
Analyze the sandbox diff for potential issues: empty values, locales missing translations that others have, and keys only partially translated. It is categorised as a Read tool in the Localization MCP Server, which means it retrieves data without modifying state.
validate_translations accepts 2 parameters: namespace, 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 validate_translations: 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.
validate_translations 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 validate_translations 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 validate_translations. 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.
validate_translations 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 →