Permanently delete one or more translation keys and ALL their associated translations from the configured Texterify project. This action is irreversible — the keys, all their translations across every language, and any tag associations are destroyed. Returns {
AI agents call delete_keys to permanently remove resources in Texterify — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes data with no undo mechanism. It destroys not just individual keys but all associated translations across all languages and tag associations in one operation. The blast radius is severe: an AI agent could wipe critical translation infrastructure with a single misguided call.
From the tool's definition Tool description explicitly states: 'Permanently delete one or more translation keys and ALL their associated translations' and 'This action is irreversible — the keys, all their translations across every language, and any tag associations are destroyed.' The…
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Permanently delete one or more translation keys and ALL their associated translations from the configured Texterify project. This action is irreversible — the keys, all their translations across every language, and any tag associations are destroyed. Returns {. It is categorised as a Destructive tool in the Texterify MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Texterify MCP server in PolicyLayer and add a rule for delete_keys: 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 Texterify. Nothing to install.
delete_keys 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_keys 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_keys. 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_keys is provided by the Texterify MCP server (mogharsallah/texterify-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 →