Update or write a translation value for a specific key
AI agents use writeTranslation to create or update resources in Weblate MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Weblate MCP Server environment.
This tool creates or modifies translation data reversibly. While it affects live translation content (warranting medium rather than low severity), the operation can be undone by writing corrected translations. The tool does not delete data, execute arbitrary code, or commit financial transactions, making Write the appropriate category.
From the tool's definition Tool name 'writeTranslation' and description 'Update or write a translation value' clearly indicate modification of data.
Documented attack patterns abuse exactly the kind of access writeTranslation gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Weblate MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for writeTranslation:
{
"version": "1",
"default": "deny",
"tools": {
"writeTranslation": {
"limits": [
{
"counter": "writetranslation_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}writeTranslation stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Update or write a translation value for a specific key. It is categorised as a Write tool in the Weblate MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Weblate MCP Server MCP server in PolicyLayer and add a rule for writeTranslation: 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 Weblate MCP Server. Nothing to install.
writeTranslation 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 writeTranslation 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 writeTranslation. 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.
writeTranslation is provided by the Weblate MCP Server MCP server (mmntm/weblate-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Weblate MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
20 Weblate MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.