If the user has previously confirmed the game information, please use the tap_web_game_uploader tool to upload the game. When user want to publish, upload, deploy, update, '发布', '上传', '部署' or '更新' project in TapTap platform. First, please use this tool to gather the game info and it will show inf...
AI agents call tap_web_game_info_gatherer to retrieve information from Tds without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| 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, if not provided, can be empty |
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 |
developerId | number | — | The developer id of the developer, if not provided, can be empty |
developerName | string | — | The name of the developer, if not provided, can be empty |
Parameters from the server's own tool schema.
The tool collects and displays game information to the user, searching directories for files like index.html. It is a preparatory read/gather step before the actual upload (which is handled by tap_web_game_uploader). No data is written, executed, or destroyed — it only gathers and presents information for user confirmation.
From the tool's definition 'gather the game info and it will show info to user, search the game directory'
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
If the user has previously confirmed the game information, please use the tap_web_game_uploader tool to upload the game. When user want to publish, upload, deploy, update, '发布', '上传', '部署' or '更新' project in TapTap platform. First, please use this tool to gather the game info and it will show info to user, search the game directory and The directory at the specified path must contain an index.html file. If it cannot be found, please prompt the user to input it. It is categorised as a Read tool in the Tds MCP Server, which means it retrieves data without modifying state.
tap_web_game_info_gatherer accepts 5 parameters: path, appId, genre, 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_info_gatherer: 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_info_gatherer 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 tap_web_game_info_gatherer 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_info_gatherer. 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_info_gatherer 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 →