AI agents use tap_web_game_uploader to create or update resources in Tds — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Tds environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
path | string | — | The absolute path of the game directory. The directory needs to contain an index.html file. |
appId | number | — | The app id of the game |
genre | string | — | If user provides a specific game genre, use it directly. If user is unsure or doesn't specify, analyze the code files, game mechanics, UI elem |
appName | string | — | The name of the app, if not provided, can be empty |
developerId | number | — | The developer id of the developer |
developerName | string | — | The name of the developer, if not provided, can be empty |
Parameters from the server's own tool schema.
This tool performs a write operation by uploading and publishing game data to the TapTap platform. It is reversible (games can typically be unpublished or replaced), so it does not qualify as Destructive. The severity is medium because misuse could result in publishing unintended or malicious game content to a public platform, but the blast radius is limited to game publication actions.
From the tool's definition Tool description states 'upload the game to TapTap platform', which creates/modifies data on an external platform. The verb 'upload' indicates a write operation that publishes game content.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
When the user confirms the game information from tap_web_game_info_gatherer, or has previously confirmed it. please use this tool to upload the game to TapTap platform. It is categorised as a Write tool in the Tds MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
tap_web_game_uploader accepts 6 parameters: path, appId, genre, appName, developerId, developerName. The full parameter table on this page comes from the server's own tool schema.
Register the Tds MCP server in PolicyLayer and add a rule for tap_web_game_uploader: 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 Tds. Nothing to install.
tap_web_game_uploader 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 tap_web_game_uploader 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 tap_web_game_uploader. 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.
tap_web_game_uploader is provided by the Tds MCP server (@taptap/tds-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →