save_deal_offer
PARTIAL SAVE: writes ONLY the 'DealOffer' field of TitlePublicConfigurationModel; all other v1/v2 fields stay untouched. Limited-time offers WITH PROGRESSION — starter packs, comeback bundles, aquarium-style chains, pick-one-of-N. Two axes: a SLOT is a UI position that cycles through its own orde...
This record as markdown: /tools/com-idosgames-platform/save-deal-offer.md
What save_deal_offer does on iDos Games
AI agents use save_deal_offer 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 | Root config of the entire Deal Offers system. Contains the slot list, the offer library and the preset registry. |
title_id | string | Yes | TitleID, для которого сохраняются данные. |
Parameters from the server's own tool schema.
Why save_deal_offer is rated Medium
An AI agent can call save_deal_offer 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.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs save_deal_offer 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_deal_offer, this is the rule to start with:
save_deal_offer 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_deal_offer call is checked against it from then on.
Questions about save_deal_offer
PARTIAL SAVE: writes ONLY the 'DealOffer' field of TitlePublicConfigurationModel; all other v1/v2 fields stay untouched. Limited-time offers WITH PROGRESSION — starter packs, comeback bundles, aquarium-style chains, pick-one-of-N. Two axes: a SLOT is a UI position that cycles through its own ordered Queue of offers (its Availability.Schedule decides how: Chained advances per player, Scheduled/Cyclic/AlwaysOn follow the wall clock, Triggered fires on an event), and an OFFER is a graph of nodes. There is no declared graph mode: the shape (single, chain, branching, choice, metered) is whatever Graph.RootNodeIDs, node NextNodeIDs, ChoiceGroupID and UnlockRules describe. Every node declares its own price as a PriceOptions dictionary — resources, crypto, a store product (real money), an AD CREDIT (that is how "watch a video" is expressed; only the server grants credits) or nothing at all, which means free. A node pays out Reward.Grants, moves offer-local Tracks and adds Reward.MilestonePoints to the offer milestone bar. Slots, offers and nodes are decomposed into named blocks (Identity, Availability, Behaviour, Graph, Milestones, Pricing, Reward), each with its own independent preset binding into DealOffer.Presets. Distinct from Store (always-on shop, no progression) and Premium (ongoing paid subscriptions). 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_deal_offer 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.
Register the iDos Games MCP server in PolicyLayer and add a rule for save_deal_offer: 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_deal_offer 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_deal_offer 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_deal_offer. 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_deal_offer 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