remove_orphan_messages

Remove target-locale messages whose keys do not exist in the source locale.

Server Paraglide weshaze/paraglide-mcp
Category Destructive
Risk class Critical
Parameters 00 required

What remove_orphan_messages does on Paraglide

AI agents call remove_orphan_messages 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.

Why remove_orphan_messages needs a policy

This tool permanently deletes translation messages from a specific locale. Deletion is irreversible and constitutes a destructive action. While the scope is limited to orphaned messages (those without source keys), an AI agent misusing this could accidentally remove legitimate translations if the source locale structure changes or is misconfigured.

From the tool's definition Tool name includes 'remove' and description states it will 'Remove target-locale messages' - this is an irreversible deletion operation that cannot be undone. The tool deletes data (messages) based on a condition (keys not in source locale).

Questions about remove_orphan_messages

What does the remove_orphan_messages tool do? +

Remove target-locale messages whose keys do not exist in the source locale. 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.

How do I enforce a policy on remove_orphan_messages? +

Register the Paraglide MCP server in PolicyLayer and add a rule for remove_orphan_messages: 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.

What risk level is remove_orphan_messages? +

remove_orphan_messages is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit remove_orphan_messages? +

Yes. Add a rate_limit block to the remove_orphan_messages 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.

How do I block remove_orphan_messages completely? +

Set action: deny in the PolicyLayer policy for remove_orphan_messages. 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.

What MCP server provides remove_orphan_messages? +

remove_orphan_messages 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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.