Clear all quality scores in a namespace to trigger fresh re-evaluation. The quality worker will re-assess all translations asynchronously. Use after updating translation content, locale skill, or AI config and need fresh quality feedback.
AI agents call reset_namespace_quality to permanently remove resources in Localization — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
namespace | string | Yes | Namespace slug |
projectSlug | string | Yes | Project slug |
Parameters from the server's own tool schema.
The tool irreversibly clears (destroys) all quality scores across an entire namespace. While the quality worker will re-assess translations asynchronously, the existing quality score data is permanently deleted — it cannot be restored to its prior state.
From the tool's definition Clear all quality scores in a namespace to trigger fresh re-evaluation
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Clear all quality scores in a namespace to trigger fresh re-evaluation. The quality worker will re-assess all translations asynchronously. Use after updating translation content, locale skill, or AI config and need fresh quality feedback. It is categorised as a Destructive tool in the Localization MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
reset_namespace_quality accepts 2 parameters: 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 reset_namespace_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.
reset_namespace_quality is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the reset_namespace_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 reset_namespace_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.
reset_namespace_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 →