get_tutorial
GET ONLY the 'Tutorial' field of TitlePublicConfigurationModel. 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), ...
This record as markdown: /tools/com-idosgames-platform/get-tutorial.md
What get_tutorial does on iDos Games
AI agents call get_tutorial to retrieve information from iDos Games without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
title_id | string | Yes | TitleID, для которого читаются данные. |
Parameters from the server's own tool schema.
Why get_tutorial is rated Low
Even though get_tutorial only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs get_tutorial 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 get_tutorial, this is the rule to start with:
get_tutorial is read-only, so it stays allowed. 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 get_tutorial call is checked against it from then on.
Questions about get_tutorial
GET ONLY the 'Tutorial' field of TitlePublicConfigurationModel. 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 Read tool in the iDos Games MCP Server, which means it retrieves data without modifying state.
get_tutorial accepts 1 parameter: title_id. Required: 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 get_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.
get_tutorial is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_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.
Set action: deny in the PolicyLayer policy for get_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.
get_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.
This server
Across the catalogue