Remove the 'expected' mark from a specific locale translation. The translation will be subject to quality checks again.
AI agents use unmark_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 unmark (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 metadata on a translation entry (removes an 'expected' mark), which is a reversible write operation. It does not delete data, execute code, or involve financial transactions. The blast radius is low since it only affects quality-check gating on a single translation entry.
From the tool's definition Remove the 'expected' mark from a specific locale translation. The translation will be subject to quality checks again.
Attacks that exploit this kind of access
Remove the 'expected' mark from a specific locale translation. The translation will be subject to quality checks again. 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.
unmark_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 unmark_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.
unmark_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 unmark_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 unmark_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.
unmark_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 →