Delete a language from a project
AI agents call delete_language to permanently remove resources in POEditor MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly removes a language and all associated translations from a POEditor project. This cannot be undone and results in permanent data loss. While the blast radius is scoped to a single project's language, the loss is complete and unrecoverable, making it Destructive rather than Write.
From the tool's definition Tool name is 'delete_language' with description 'Delete a language from a project'. The verb 'delete' combined with the destructive operation of removing an entire language from a translation project indicates irreversible data removal.
Attacks that exploit this kind of access
Delete a language from a project. It is categorised as a Destructive tool in the POEditor MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the POEditor MCP Server MCP server in PolicyLayer and add a rule for delete_language: 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 POEditor MCP Server. Nothing to install.
delete_language 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 delete_language 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 delete_language. 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.
delete_language is provided by the POEditor MCP Server MCP server (r-pedraza/poeditor-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 →