save_localization_keys
Create or update localization keys in the title's DEFAULT language. PARTIAL: only the keys you send are written, the rest of the table is untouched — people translate the same table, and replacing it wholesale would erase their work. Write ONLY the default language: other locales are filled by tr...
This record as markdown: /tools/com-idosgames-platform/save-localization-keys.md
What save_localization_keys does on iDos Games
AI agents use save_localization_keys to create or update resources in iDos Games, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your iDos Games environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
keys | object | Yes | Object of localization key → text in the DEFAULT language. Only these keys are written. |
title_id | string | Yes | TitleID. |
Parameters from the server's own tool schema.
Why save_localization_keys is rated Medium
An AI agent can call save_localization_keys faster than any human can review: one bad instruction and it creates or modifies resources in iDos Games by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs save_localization_keys safely
PolicyLayer is an MCP gateway: it sits between your AI agents and iDos Games, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For save_localization_keys, this is the rule to start with:
save_localization_keys 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 iDos Games, apply this rule, and every save_localization_keys call is checked against it from then on.
Questions about save_localization_keys
Create or update localization keys in the title's DEFAULT language. PARTIAL: only the keys you send are written, the rest of the table is untouched — people translate the same table, and replacing it wholesale would erase their work. Write ONLY the default language: other locales are filled by translators or by the dashboard's machine translation, and a string that exists only in a target language never appears in the coverage report. Keys are free-form; a dotted namespace ("shop.button.buy") keeps a large table readable. It is categorised as a Write tool in the iDos Games MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
save_localization_keys accepts 2 parameters: keys, title_id. Required: keys, title_id. The full parameter table on this page comes from the server's own tool schema.
Register the iDos Games MCP server in PolicyLayer and add a rule for save_localization_keys: 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 iDos Games. Nothing to install.
save_localization_keys 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 save_localization_keys 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 save_localization_keys. 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.
save_localization_keys is provided by the iDos Games MCP server (https://site.idosgames.com/api/v2/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on iDos Games, and thousands of servers like it.
This server
Across the catalogue