AI agents use set_translation_state 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 performs a state modification operation, which is characteristic of Write category tools—it updates existing data reversibly. While the blast radius is limited to translation workflow state changes (not deletion, not financial impact, not code execution), misconfiguration or misuse could disrupt translation workflows by setting incorrect states on translations.
From the tool's definition The tool "set_translation_state" modifies the state attribute of an existing translation object within the Tolgee localization platform. This is a reversible change to translation metadata (state/status) rather than deletion or creation of new records.
Attacks that exploit this kind of access
Set the state of a specific translation. 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 set_translation_state: 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.
set_translation_state 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_state 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_state. 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_state 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 →