save_title_data
Write the authored (Static) part of the title's key-value data store. REPLACES the whole bucket: read it with get_title_data first and send it back extended, or omitted keys are deleted. The Runtime scope CANNOT be written here — mutable title state is owned by CloudCode scripts, so their counter...
This record as markdown: /tools/com-idosgames-platform/save-title-data.md
What save_title_data does on iDos Games
AI agents use save_title_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 |
|---|---|---|---|
bucket | string | Yes | Public = readable by game clients; Private = server/CloudCode only. |
values | object | Yes | Object of key → string value. Replaces the whole bucket. JSON-encode structured values yourself. |
title_id | string | Yes | TitleID. |
Parameters from the server's own tool schema.
Why save_title_data is rated Medium
An AI agent can call save_title_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_title_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_title_data, this is the rule to start with:
save_title_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_title_data call is checked against it from then on.
Questions about save_title_data
Write the authored (Static) part of the title's key-value data store. REPLACES the whole bucket: read it with get_title_data first and send it back extended, or omitted keys are deleted. The Runtime scope CANNOT be written here — mutable title state is owned by CloudCode scripts, so their counters are never overwritten behind their back. Register keys in the TitleCustomData config section (save_title_custom_data) for type validation, limits, TTL and defaults. 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_title_data accepts 3 parameters: bucket, values, title_id. Required: bucket, values, 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_title_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_title_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_title_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_title_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_title_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