Retrieve a single translation key with all its translations across every project language, plus related tags and placeholders. Use this to inspect the complete translation state of a specific key before updating or to verify translations after setting them. The response includes:
AI agents call get_key to retrieve information from Texterify without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves translation data for a specific key, returning its translations, tags, and placeholders. It performs a query operation with no side effects—no data is created, modified, deleted, or executed. Despite the server's broader capabilities (create, update, delete operations available on sibling tools), this specific tool is purely read-only.
From the tool's definition Tool name 'get_key' and description explicitly states 'Retrieve a single translation key' with no modification, deletion, or execution capabilities. The description emphasizes inspection and verification without side effects.
Attacks that exploit this kind of access
Retrieve a single translation key with all its translations across every project language, plus related tags and placeholders. Use this to inspect the complete translation state of a specific key before updating or to verify translations after setting them. The response includes:. It is categorised as a Read tool in the Texterify MCP Server, which means it retrieves data without modifying state.
Register the Texterify MCP server in PolicyLayer and add a rule for get_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 Texterify. Nothing to install.
get_key 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 get_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 get_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.
get_key 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 →