save_workshop

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-workshop.md

WHAT IT DOES

What save_workshop does on iDos Games

AI agents use save_workshop 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	Title Workshop configuration: a catalog of content made by players (maps, levels, skins, models) and by the publisher (official content). Unlike the Marketplace
`title_id`	string	Yes	TitleID, для которого сохраняются данные.

Parameters from the server's own tool schema.

RISK

Why save_workshop is rated Medium

An AI agent can call save_workshop 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 signalsHigh parameter count (12 properties) · Bulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs save_workshop 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_workshop, this is the rule to start with:

save_workshop Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "save_workshop": {
      "limits": [
        {
          "counter": "save_workshop_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect iDos Games, apply this rule, and every save_workshop call is checked against it from then on.

FAQ

Questions about save_workshop

What does the save_workshop tool do? +

PARTIAL SAVE: writes ONLY the 'Workshop' field of TitlePublicConfigurationModel; all other v1/v2 fields stay untouched. Workshop - the catalog of content made by PLAYERS (maps, levels, skins, models, any file the game defines) and by the publisher (official content), and the LICENSES to it. Nothing is transferred: acquiring grants a license to a digital copy, so one publication is acquired by many and the author keeps it (unlike Marketplace, which escrows and moves goods). ContentTypes is the game-specific part: each type id (e.g. 'voxelcraft.world') declares its file roles (AllowedMimeTypes, MaxBytes, MaxCount, Required; the engine checks the uploaded file's signature against the declared type), whether a thumbnail is required, which AccessModes authors may use, an optional per-type PricePolicy, a PublishGate (SegmentGate: who may publish), PublishFeeOptions (PriceOption, Standard part only, never store-paid), a TagVocabulary and per-player limits. An author gives access by ANY of several options: Free, Price (a ResourceBundle validated by PricePolicy; the buyer pays, the author receives it minus Commission, which is burned or credited to the MarketplaceLedger) or Holding (hold N of a currency/item - nothing is charged; Mode WhileHeld re-checks on every download, UnlockOnce checks once and grants a permanent license; HoldingPolicy whitelists usable resources). Moderation: BlockedTerms for titles/descriptions/tags, AutoHideReportThreshold (reports that hide a publication until reviewed), RequireApproval (pre-moderation). Featured lists publisher-curated collections with their own ScheduleSpec and SegmentGate. Publications, licenses, reactions and reports are NOT here - they are operational data in their own collections; files live in a private bucket configured by the engine's WORKSHOP_BUCKET_NAME env var. 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_workshop accept? +

save_workshop 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_workshop? +

Register the iDos Games MCP server in PolicyLayer and add a rule for save_workshop: 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_workshop? +

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

Can I rate-limit save_workshop? +

Yes. Add a rate_limit block to the save_workshop 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_workshop completely? +

Set action: deny in the PolicyLayer policy for save_workshop. 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_workshop? +

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

KEEP EXPLORING

More on iDos Games, and thousands of servers like it.

This server

All 159 iDos Games tools →

Across the catalogue

save_snapshot on Why Did You Render → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →