New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

save_tutorial

PARTIAL SAVE: writes ONLY the 'Tutorial' field of TitlePublicConfigurationModel; all other v1/v2 fields stay untouched. Tutorial / onboarding definitions — flows (ordered scenarios) built from steps that teach the player a mechanic. A step completes either by client acknowledgement or by a real g...

SERVERiDos Games SOURCEhttps://site.idosgames.com/api/v2/mcp
Medium RISK CLASS
Category Write
Parameters 22 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-idosgames-platform/save-tutorial.md

What save_tutorial does on iDos Games

AI agents use save_tutorial 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.

ParameterTypeRequiredDescription
value object Yes Root block of the tutorial (onboarding) system in the title config.
title_id string Yes TitleID, для которого сохраняются данные.

Parameters from the server's own tool schema.

Why save_tutorial is rated Medium

An AI agent can call save_tutorial 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.

Questions about save_tutorial

What does the save_tutorial tool do? +

PARTIAL SAVE: writes ONLY the 'Tutorial' field of TitlePublicConfigurationModel; all other v1/v2 fields stay untouched. Tutorial / onboarding definitions — flows (ordered scenarios) built from steps that teach the player a mechanic. A step completes either by client acknowledgement or by a real game event (the same TriggerSource vocabulary as Quest), so "make a roll", "buy something", "open a chest" need no client-side bookkeeping. A step may also PREDETERMINE the outcome of another module (TutorialScriptedOutcome — e.g. force the board dice to land on a Raid tile), which is the only way to demonstrate a mechanic instead of randomness. Flows carry an audience gate (SegmentGate) and a schedule (ScheduleSpec); putting an Experiment condition in that gate is how two tutorial versions are A/B-tested. Gating other content on tutorial progress is done via SegmentGate.Tutorial per entity, or via Settings.Blocking to close whole modules until onboarding is finished. 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.

What parameters does save_tutorial accept? +

save_tutorial 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.

How do I enforce a policy on save_tutorial? +

Register the iDos Games MCP server in PolicyLayer and add a rule for save_tutorial: 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.

What risk level is save_tutorial? +

save_tutorial is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit save_tutorial? +

Yes. Add a rate_limit block to the save_tutorial 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.

How do I block save_tutorial completely? +

Set action: deny in the PolicyLayer policy for save_tutorial. 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.

What MCP server provides save_tutorial? +

save_tutorial 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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of iDos Games's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.