Mark a specific locale translation as manually accepted ('expected'). This suppresses quality warnings for this key+locale — useful when the AI quality check flags it but a human has verified the translation is correct. Quality checks will skip locales marked as expected.
AI agents use mark_expected to create or update resources in Localization — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Localization environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
key | string | Yes | Translation key |
locale | string | Yes | Locale code to mark as expected (e.g. 'nb-NO') |
namespace | string | Yes | Namespace slug |
projectSlug | string | Yes | Project slug |
Parameters from the server's own tool schema.
This tool modifies localization metadata by setting an 'expected' flag on translations, which affects how quality checks behave. It is reversible (the flag can presumably be unset), so it falls into Write rather than Destructive.
From the tool's definition Tool marks a translation as 'manually accepted' and 'suppresses quality warnings', modifying the state of quality-check behavior for a specific locale.
Attacks that exploit this kind of access
Mark a specific locale translation as manually accepted ('expected'). This suppresses quality warnings for this key+locale — useful when the AI quality check flags it but a human has verified the translation is correct. Quality checks will skip locales marked as expected. It is categorised as a Write tool in the Localization MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
mark_expected accepts 4 parameters: key, locale, namespace, projectSlug. Required: key, locale, 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 mark_expected: 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.
mark_expected is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the mark_expected 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 mark_expected. 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.
mark_expected 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 →