This record as markdown: /tools/yanhuifair-godot-mcp/create-translation.md
What create_translation does on Godot
AI agents use create_translation to create or update resources in Godot, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Godot environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
keys | object | — | Initial translation keys to add |
path | string | Yes | Output path for new translation .csv file (e.g. "localization/zh_CN.csv") |
language | object | — | Language code (e.g. "en", "zh_CN", "ja") |
Parameters from the server's own tool schema.
Why create_translation is rated Medium
This tool writes a new translation file (CSV format) to the system. This is a Write-category operation because it creates/modifies project data reversibly—translation files can be edited, deleted, or regenerated. It does not execute code, delete irreversibly, or move money.
From the tool's definition create_translation creates a translation CSV file, which is a write operation that modifies or creates data reversibly. The description explicitly states 'Create translation CSV', indicating data creation.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs create_translation safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Godot, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_translation, this is the rule to start with:
create_translation 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Godot, apply this rule, and every create_translation call is checked against it from then on.
Questions about create_translation
Create translation CSV. It is categorised as a Write tool in the Godot MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
create_translation accepts 3 parameters: keys, path, language. Required: path. The full parameter table on this page comes from the server's own tool schema.
Register the Godot MCP server in PolicyLayer and add a rule for create_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 Godot. Nothing to install.
create_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 create_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 create_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.
create_translation is provided by the Godot MCP server (@yanhuifair/godot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Godot, and thousands of servers like it.
This server
Across the catalogue