save_reward
PARTIAL SAVE: writes ONLY the 'Reward' field of TitlePublicConfigurationModel; all other v1/v2 fields stay untouched. Reward templates — reusable bundles of currency + items + buffs that can be granted to a player. Referenced by Quest, TimedEvent, CoopEvent, Season, DailyLogin, Referral, etc. Def...
This record as markdown: /tools/com-idosgames-platform/save-reward.md
What save_reward does on iDos Games
AI agents use save_reward 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 for universal, system-agnostic rewards. Umbrella over four independent subsystems: DailyCalendars, IdleAccruals, Comebacks, Claims. |
title_id | string | Yes | TitleID, для которого сохраняются данные. |
Parameters from the server's own tool schema.
Why save_reward is rated Medium
An AI agent can call save_reward 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_reward 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_reward, this is the rule to start with:
save_reward 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_reward call is checked against it from then on.
Questions about save_reward
PARTIAL SAVE: writes ONLY the 'Reward' field of TitlePublicConfigurationModel; all other v1/v2 fields stay untouched. Reward templates — reusable bundles of currency + items + buffs that can be granted to a player. Referenced by Quest, TimedEvent, CoopEvent, Season, DailyLogin, Referral, etc. Define a reward once here, then reference it everywhere instead of inlining payouts. 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_reward 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_reward: 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_reward 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_reward 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_reward. 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_reward 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