Critical-risk tools in Localization
7 of the 46 tools in Localization are classified as critical risk. This page profiles those tools specifically, with recommended policy actions and the attack patterns that target them.
Every operation listed below is an action PolicyLayer recommends controlling at the transport layer. Open any tool to see the full profile, risk score, and YAML policy snippet.
Tools at critical risk
-
delete_localeDestructiveRemove a locale from a project. This deletes ALL translation values for that locale across all namespaces. This is a destructive operation — use with caution. The default locale...
-
delete_namespaceDestructiveDelete a namespace from a project. This cascades to ALL keys and values in the namespace. This is a destructive and irreversible operation.
-
delete_translationDestructiveDelete one or more translation keys from the sandbox (soft delete). Keys remain in production until you promote the sandbox.
-
delete_webhookDestructiveDelete a webhook configuration. This permanently removes the webhook and stops all future deliveries.
-
reset_namespace_qualityDestructiveClear 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...
-
reset_namespace_translationsDestructiveDelete sandbox translations and trigger re-translation. Scope: namespace (no params), single locale ({ locale }), multiple locales ({ locales: ["de","fr"] }), or single key+loca...
-
reset_sandboxDestructiveDiscard all sandbox changes and re-copy from current production state. This destroys all pending sandbox edits. Requires confirmed: true.
Attacks that target this class
Critical-risk tools in any server share these documented attack patterns. Each links to the full case and the defensive policy.