AI agents call strings_list_keys to retrieve information from Phrase without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves/lists data from a localization project without modifying, deleting, or executing operations. It is a straightforward read operation with minimal blast radius if misused by an AI agent.
From the tool's definition Tool name contains 'list' and description states 'List keys in a Phrase Strings project' — a query operation with no side effects.
Attacks that exploit this kind of access
List keys in a Phrase Strings project. It is categorised as a Read tool in the Phrase MCP Server, which means it retrieves data without modifying state.
Register the Phrase MCP server in PolicyLayer and add a rule for strings_list_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_list_keys is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the strings_list_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_list_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_list_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 →