get_store
GET ONLY the 'Store' field of TitlePublicConfigurationModel. In-game shop, built as a tree: Stores -> Layout.Sections -> Slots, plus a flat StoreOffers catalogue. A SLOT is the only address a product can be bought through, and it decides what stands in it: Rotation.Mode is Fixed (a pinned product...
This record as markdown: /tools/com-idosgames-platform/get-store.md
What get_store does on iDos Games
AI agents call get_store 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 |
|---|---|---|---|
title_id | string | Yes | TitleID, для которого читаются данные. |
Parameters from the server's own tool schema.
Why get_store is rated Low
Even though get_store 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_store 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_store, this is the rule to start with:
get_store 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_store call is checked against it from then on.
Questions about get_store
GET ONLY the 'Store' field of TitlePublicConfigurationModel. In-game shop, built as a tree: Stores -> Layout.Sections -> Slots, plus a flat StoreOffers catalogue. A SLOT is the only address a product can be bought through, and it decides what stands in it: Rotation.Mode is Fixed (a pinned product - an ordinary shelf), Title (everyone sees the same roll) or Player (a personal roll), with a weighted Pool and an optional per-window purchase cap. The refresh window is a ScheduleSpec on the slot. A product not placed in any slot cannot be bought at all. Price is always a PriceOptions dictionary and can be virtual currency, crypto, a store product (real money), an ad credit, or FREE - an unset Cost means free, and a free product must be limited on some axis. Pricing.CompareAt is a struck-through price for display only and never reaches the charge. Identity.Tags and Identity.CustomParams are badges and ribbons the server never interprets. Distinct from Premium (real-money tiered offers) and DealOffer (limited-time promotions with progression). It is categorised as a Read tool in the iDos Games MCP Server, which means it retrieves data without modifying state.
get_store accepts 1 parameter: 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_store: 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_store 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_store 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_store. 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_store 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