Add new languages or sync existing translations via LangAPI. Use this tool to: (1) ADD translations for new languages like Czech, Spanish, French - creates new locale files automatically, (2) SYNC existing translations when source content changes. Supports any valid language code (e.g.,
AI agents use sync_translations to create or update resources in Langapi — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Langapi environment.
This tool performs reversible write operations: it creates new translation files and modifies existing translation content. While these are persistent changes to the project's i18n infrastructure, they can be undone (files can be deleted, translations can be corrected in subsequent syncs). It does not execute arbitrary code, delete data irreversibly, or move money.
From the tool's definition Tool description states it can "Add new languages" (creates locale files) and "SYNC existing translations" (modifies translation data). Key verbs: 'creates new locale files automatically' and 'sync existing translations'.
Attacks that exploit this kind of access
Add new languages or sync existing translations via LangAPI. Use this tool to: (1) ADD translations for new languages like Czech, Spanish, French - creates new locale files automatically, (2) SYNC existing translations when source content changes. Supports any valid language code (e.g.,. It is categorised as a Write tool in the Langapi MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Langapi MCP server in PolicyLayer and add a rule for sync_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 Langapi. Nothing to install.
sync_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 sync_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 sync_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.
sync_translations is provided by the Langapi MCP server (tedyhub/langapi-mcp-server). 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 →