Remove translation keys from a job in a Phrase Strings project.
AI agents call strings_remove_job_keys 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.
Removing translation keys is a destructive operation that cannot be undone without restore/backup. While not cascading across the entire system, it permanently deletes structured data within a Phrase project, affecting translation workflows. This warrants high severity and Destructive classification.
From the tool's definition Tool name 'strings_remove_job_keys' explicitly uses 'remove', and description states 'Remove translation keys from a job' — this irreversibly deletes data from a localization project.
Attacks that exploit this kind of access
Remove translation keys from a job 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_remove_job_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 Phrase. Nothing to install.
strings_remove_job_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 strings_remove_job_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 strings_remove_job_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.
strings_remove_job_keys 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 →