AI agents use create_or_update_translations to create or update resources in Tolgee — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Tolgee environment.
This tool modifies translation content within a localization system. While the operation is reversible (translations can be updated or reverted), it affects live or production translation data that end-users may depend on. The high severity reflects the potential impact of incorrect or malicious translations on application functionality and user experience across multiple languages.
From the tool's definition Tool name 'create_or_update_translations' and context as part of a localization platform API that manages translation projects. The 'create_or_update' pattern indicates reversible modification of translation data.
Attacks that exploit this kind of access
create_or_update_translations. It is categorised as a Write tool in the Tolgee MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Tolgee MCP server in PolicyLayer and add a rule for create_or_update_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 Tolgee. Nothing to install.
create_or_update_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_or_update_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_or_update_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_or_update_translations is provided by the Tolgee MCP server (ytarfa/tolgee-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 →