create_title
Create a NEW game (Title) on the publisher's account, the same way the dashboard does. It takes a slot of the publisher's plan, gets the base (sign-in + lobby with profile, inventory, invites, friends, quests, mailbox) plus a game module, a ready starter build playable at once on its own address,...
This record as markdown: /tools/com-idosgames-platform/create-title.md
What create_title does on iDos Games
AI agents use create_title 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 |
|---|---|---|---|
idea | string | — | What the game is about, in a few sentences (up to 4000 characters). Used as the description and to pick the base game and category when they are not given. |
name | string | Yes | Game name shown to players, up to 50 characters. |
category | string | — | Optional catalog category id (e.g. 'shooter'). An unknown id fails with the list of valid ones. |
base_game | string | — | Optional starter game module the project is built on (see list_modules). Omit to let the platform pick it from the idea. |
Parameters from the server's own tool schema.
Why create_title is rated Medium
An AI agent can call create_title 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.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs create_title 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 create_title, this is the rule to start with:
create_title 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 create_title call is checked against it from then on.
Questions about create_title
Create a NEW game (Title) on the publisher's account, the same way the dashboard does. It takes a slot of the publisher's plan, gets the base (sign-in + lobby with profile, inventory, invites, friends, quests, mailbox) plus a game module, a ready starter build playable at once on its own address, and a DEV sandbox copy. The new Title and its '-DEV' copy are added to THIS connection right away, so pass the returned TitleID as title_id to get_<section> / save_<section> and the build tools next. Give a name and the idea; optionally base_game (a starter game module id: mini-game, board-game, idle-rpg, hero-run, voxelcraft, video-studio; otherwise it is picked from the idea) and category. Not idempotent: every successful call creates another game, so do not retry a call that succeeded. When the plan has no free slot it fails with TITLE_LIMIT_REACHED and a link where the publisher can upgrade. No token is launched (that needs the publisher's own wallet in the dashboard). Takes no title_id; needs the 'title:create' permission. 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.
create_title accepts 4 parameters: idea, name, category, base_game. Required: name. 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 create_title: 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.
create_title 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 create_title 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 create_title. 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.
create_title 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