AI agents use create_key_with_translations 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.
This tool creates new translation keys and sets translations, which are reversible write operations. While it modifies the translation management system, it does not delete data (which would be Destructive) or execute arbitrary code (Execute).
From the tool's definition Tool name 'create_key_with_translations' and description 'Create a new translation key and set translations for multiple languages in a single operation' explicitly states it creates new data (translation keys and their values).
Attacks that exploit this kind of access
Create a new translation key and set translations for multiple languages in a single operation. 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 create_key_with_translations: 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.
create_key_with_translations 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 create_key_with_translations 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 create_key_with_translations. 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.
create_key_with_translations 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 →