Create a new translation key (i18n string identifier) in the configured Texterify project. This only creates the key entry — it does NOT add any translated content. After creating a key, call set_translation for each language to add translations. Key names must be unique within the project; dupli...
AI agents use create_key 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.
The tool creates new translation keys (i18n identifiers) in the Texterify project, which is a reversible write operation. While there are destructive tools available on the same server (delete_keys), this specific tool only creates entries without deleting or overwriting existing data. It falls into the Write category as a data creation operation.
From the tool's definition Tool description states it 'Create a new translation key' which modifies the translation management system by adding a new entry to the configured project.
Attacks that exploit this kind of access
Create a new translation key (i18n string identifier) in the configured Texterify project. This only creates the key entry — it does NOT add any translated content. After creating a key, call set_translation for each language to add translations. Key names must be unique within the project; duplicate names return a validation error with code. 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: 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 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 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. 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 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 →