Update a translation
AI agents use update_translation to create or update resources in POEditor MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your POEditor MCP Server environment.
The tool modifies translation data without deleting or destroying it. Updates are reversible (the previous translation can be restored), distinguishing this from Destructive category. It does not execute arbitrary code, move money, or merely read data. Write category is appropriate for data modification operations that can be undone.
From the tool's definition Tool name 'update_translation' and description 'Update a translation' indicate modification of existing data. Sibling tools include destructive operations (delete_translation, delete_project), but this tool itself performs a reversible update operation.
Attacks that exploit this kind of access
Update a translation. It is categorised as a Write tool in the POEditor MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the POEditor MCP Server MCP server in PolicyLayer and add a rule for update_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 POEditor MCP Server. Nothing to install.
update_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 update_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 update_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.
update_translation is provided by the POEditor MCP Server MCP server (r-pedraza/poeditor-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 →