Translate file content while preserving structure and format. Supports JSON, YAML, XML, CSV, TXT, MD, and other text files
AI agents use translate_file to create or update resources in i18n Agent — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your i18n Agent environment.
This tool reads a file and writes translated content, modifying or creating file data. It preserves structure which implies it produces output files. This is a Write operation as it creates/modifies file content. Severity is medium because an AI agent misusing this could overwrite source files with incorrect translations, but it is generally reversible through version control or backups.
From the tool's definition Translate file content while preserving structure and format
Attacks that exploit this kind of access
Translate file content while preserving structure and format. Supports JSON, YAML, XML, CSV, TXT, MD, and other text files. It is categorised as a Write tool in the i18n Agent MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the i18n Agent MCP server in PolicyLayer and add a rule for translate_file: 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 i18n Agent. Nothing to install.
translate_file 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 translate_file 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 translate_file. 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.
translate_file is provided by the i18n Agent MCP server (loking/mcp-client). 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 →