save_user_custom_data
PARTIAL SAVE: writes ONLY the 'UserCustomData' field of TitlePublicConfigurationModel; all other v1/v2 fields stay untouched. Schema for per-player custom data fields — name, type, default value, visibility, whether the client can write it. This is the SCHEMA only; actual per-user values live on ...
This record as markdown: /tools/com-idosgames-platform/save-user-custom-data.md
What save_user_custom_data does on iDos Games
AI agents use save_user_custom_data 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 | Configuration of the Custom User Data V2 system (arbitrary user records). Hybrid architecture combining bucket-based privacy separation (Private/Public/ReadOnly |
title_id | string | Yes | TitleID, для которого сохраняются данные. |
Parameters from the server's own tool schema.
Why save_user_custom_data is rated Medium
An AI agent can call save_user_custom_data 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_user_custom_data 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_user_custom_data, this is the rule to start with:
save_user_custom_data 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_user_custom_data call is checked against it from then on.
Questions about save_user_custom_data
PARTIAL SAVE: writes ONLY the 'UserCustomData' field of TitlePublicConfigurationModel; all other v1/v2 fields stay untouched. Schema for per-player custom data fields — name, type, default value, visibility, whether the client can write it. This is the SCHEMA only; actual per-user values live on the User document. Use this to declare new player-specific stats, flags, or progress counters. 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_user_custom_data 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_user_custom_data: 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_user_custom_data 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_user_custom_data 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_user_custom_data. 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_user_custom_data 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