Run AI quality check on multiple keys in a namespace at once. When keys is omitted, checks ALL keys in the namespace. Results are persisted to the database and visible in Admin UI. Use this after bulk translate or bulk import to verify translation quality at scale. For a single key use check_entr...
AI agents use bulk_check_quality 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 |
|---|---|---|---|
keys | array | — | Keys to check (1–500). When omitted, all keys in the namespace are checked. |
namespace | string | Yes | Namespace slug |
projectSlug | string | Yes | Project slug |
Parameters from the server's own tool schema.
While the primary action is reading/analyzing translation quality, the tool explicitly persists results to the database, making it a Write operation. It modifies stored state by saving quality check results. The blast radius is medium — misuse could pollute quality check records for an entire namespace (all keys if 'keys' is omitted), but it doesn't delete or overwrite actual translation content.
From the tool's definition Results are persisted to the database and visible in Admin UI
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
Run AI quality check on multiple keys in a namespace at once. When keys is omitted, checks ALL keys in the namespace. Results are persisted to the database and visible in Admin UI. Use this after bulk translate or bulk import to verify translation quality at scale. For a single key use check_entry_quality instead. 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.
bulk_check_quality accepts 3 parameters: keys, namespace, projectSlug. Required: 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 bulk_check_quality: 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.
bulk_check_quality 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 bulk_check_quality 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 bulk_check_quality. 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.
bulk_check_quality 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 →