get_localization_keys
List the title's localization KEYS with their text in the DEFAULT language, plus the configured locales. Call it before writing any user-visible string so you reuse an existing key instead of inventing a second one for the same label. Filter with "prefix" ("shop.", "quest."); long tables are trun...
This record as markdown: /tools/com-idosgames-platform/get-localization-keys.md
What get_localization_keys does on iDos Games
AI agents call get_localization_keys to retrieve information from iDos Games without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
prefix | string | — | Optional key prefix filter. |
title_id | string | Yes | TitleID. |
Parameters from the server's own tool schema.
Why get_localization_keys is rated Low
Even though get_localization_keys only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs get_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 get_localization_keys, this is the rule to start with:
get_localization_keys is read-only, so it stays allowed. 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 get_localization_keys call is checked against it from then on.
Questions about get_localization_keys
List the title's localization KEYS with their text in the DEFAULT language, plus the configured locales. Call it before writing any user-visible string so you reuse an existing key instead of inventing a second one for the same label. Filter with "prefix" ("shop.", "quest."); long tables are truncated and say so. The client resolves text as t(x) = player's table -> fallback table -> x itself, which is why a plain literal still renders — a literal is simply a key with no translation. It is categorised as a Read tool in the iDos Games MCP Server, which means it retrieves data without modifying state.
get_localization_keys accepts 2 parameters: prefix, title_id. Required: 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 get_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.
get_localization_keys is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_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 get_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.
get_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