Delete an existing translation key in a Phrase Strings project.
AI agents call strings_delete_key to permanently remove resources in Phrase — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting a translation key is a destructive operation that cannot be undone without external recovery mechanisms. The blast radius is high because removing keys from a localization project breaks translations and affects all downstream products using those strings. This is more severe than Write (which is reversible) and warrants the Destructive category.
From the tool's definition Tool name contains 'delete' and description explicitly states 'Delete an existing translation key' — this is an irreversible removal of data from a localization project.
Attacks that exploit this kind of access
Delete an existing translation key in a Phrase Strings project. It is categorised as a Destructive tool in the Phrase MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Phrase MCP server in PolicyLayer and add a rule for strings_delete_key: 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 Phrase. Nothing to install.
strings_delete_key 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 strings_delete_key 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 strings_delete_key. 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.
strings_delete_key is provided by the Phrase MCP server (phrase-mcp-server). 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 →