save_localization

SERVERiDos Games SOURCEhttps://site.idosgames.com/api/v2/mcp

Medium RISK CLASS

Category Write

Parameters 22 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-idosgames-platform/save-localization.md

WHAT IT DOES

What save_localization does on iDos Games

AI agents use save_localization 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
`value`	object	Yes	Localization settings of the title. The translation TABLES are not stored here: they live in the separate TitleLocalization collection (one document per title+l
`title_id`	string	Yes	TitleID, для которого сохраняются данные.

Parameters from the server's own tool schema.

RISK

Why save_localization is rated Medium

An AI agent can call save_localization 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

RECOMMENDED RULE

The rule that runs save_localization 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, this is the rule to start with:

save_localization Rate-limited

save_localization 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "save_localization": {
      "limits": [
        {
          "counter": "save_localization_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect iDos Games, apply this rule, and every save_localization call is checked against it from then on.

FAQ

Questions about save_localization

What does the save_localization tool do? +

PARTIAL SAVE: writes ONLY the 'Localization' field of TitlePublicConfigurationModel; all other v1/v2 fields stay untouched. Localization SETTINGS — which locales the title offers, which one is the default (and therefore the fallback), what to render for a missing key, and the store limits. The translation TABLES are deliberately NOT here: they live in the separate TitleLocalization collection (one document per title+locale) and are delivered one file per locale, because text changes far more often than balance and must not invalidate the whole title config. Client resolution is t(x) = own table -> fallback table -> x itself, which is why a title whose DisplayName fields hold literal names keeps working unchanged: a literal is simply a key with no translation. Add or edit translations through the Localization endpoints, not through this section. 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.

What parameters does save_localization accept? +

save_localization accepts 2 parameters: value, title_id. Required: value, title_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on save_localization? +

Register the iDos Games MCP server in PolicyLayer and add a rule for save_localization: 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.

What risk level is save_localization? +

save_localization is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit save_localization? +

Yes. Add a rate_limit block to the save_localization 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.

How do I block save_localization completely? +

Set action: deny in the PolicyLayer policy for save_localization. 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.

What MCP server provides save_localization? +

save_localization 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.

KEEP EXPLORING

More on iDos Games, and thousands of servers like it.

This server

All 159 iDos Games tools →

Across the catalogue

save_snapshot on Why Did You Render → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →