finish_build_upload

SERVERiDos Games SOURCEhttps://site.idosgames.com/api/v2/mcp

High RISK CLASS

Category Execute

Parameters 42 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-idosgames-platform/finish-build-upload.md

WHAT IT DOES

What finish_build_upload does on iDos Games

AI agents invoke finish_build_upload to trigger actions in iDos Games. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

Parameter	Type	Required	Description
`label`	string	—	Optional short name of the version shown in the history ("Added the shop").
`deploy`	boolean	—	true = put this version live for players as soon as it is unpacked. Default false: only a test version.
`build_id`	string	Yes	build_id returned by begin_build_upload.
`title_id`	string	Yes	Live TitleID (the same one passed to begin_build_upload).

Parameters from the server's own tool schema.

RISK

Why finish_build_upload is rated High

finish_build_upload triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

finish_build_upload Rate-limited

finish_build_upload stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "finish_build_upload": {
      "limits": [
        {
          "counter": "finish_build_upload_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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 finish_build_upload call is checked against it from then on.

FAQ

Questions about finish_build_upload

What does the finish_build_upload tool do? +

Finish an upload started with begin_build_upload: unpacks the zip into a new version of the Title (it appears in the dashboard's version history) and waits up to ~100 s. Returns the version with a TestUrl to try it before players see it. deploy=true also puts it live for players on the Title's address and its idosgames.com page. If it is still unpacking when the call returns, poll get_build. Calling it again with the same build_id returns the same version (with deploy=true it deploys a version that is ready). It is categorised as a Execute tool in the iDos Games MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

What parameters does finish_build_upload accept? +

finish_build_upload accepts 4 parameters: label, deploy, build_id, title_id. Required: build_id, title_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on finish_build_upload? +

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

finish_build_upload is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit finish_build_upload? +

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

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

finish_build_upload 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 → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →