Set the translated text for a specific key in a specific language (upsert). If a translation already exists for the key+language pair it is updated; otherwise a new translation is created. Requires both a key_id (from list_keys, get_key, or create_key) and a language_id (from list_languages). For...
AI agents use set_translation to create or update resources in Texterify — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Texterify environment.
set_translation creates or modifies translation values, which are data changes that can be undone (updated or deleted via other tools like delete_keys or update_key). This is characteristic of Write operations rather than Read (no query-only), Destructive (changes are reversible), Execute (no arbitrary code/commands), Financial (no monetary operations), or Other.
From the tool's definition Tool description explicitly states it performs an 'upsert' operation: 'If a translation already exists for the key+language pair it is updated; otherwise a new translation is created.' This is reversible modification of translation data.
Attacks that exploit this kind of access
Set the translated text for a specific key in a specific language (upsert). If a translation already exists for the key+language pair it is updated; otherwise a new translation is created. Requires both a key_id (from list_keys, get_key, or create_key) and a language_id (from list_languages). For keys with pluralization_enabled, provide plural forms alongside the main content — which forms to use depends on the target language. It is categorised as a Write tool in the Texterify MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Texterify MCP server in PolicyLayer and add a rule for set_translation: 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.
set_translation is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the set_translation 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 set_translation. 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.
set_translation 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 →