Remove a locale from the project settings and delete its message file.
AI agents call remove_locale to permanently remove resources in Paraglide — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently deletes a locale's message file and modifies project settings, actions that cannot be undone without external backup/recovery. This is the most severe category applicable. The blast radius is high: an AI agent could accidentally or maliciously remove critical locales, destroying translations for entire languages and breaking multi-language support in the project.
From the tool's definition Tool description states 'Remove a locale from the project settings and delete its message file.' The verbs 'remove' and 'delete' indicate irreversible deletion of configuration and data files.
Attacks that exploit this kind of access
Remove a locale from the project settings and delete its message file. It is categorised as a Destructive tool in the Paraglide MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Paraglide MCP server in PolicyLayer and add a rule for remove_locale: 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 Paraglide. Nothing to install.
remove_locale 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 remove_locale 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 remove_locale. 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.
remove_locale is provided by the Paraglide MCP server (weshaze/paraglide-mcp). 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 →