AI agents use tap_create_app 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 |
|---|---|---|---|
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 |
developerId | number | — | The developer id of the app |
Parameters from the server's own tool schema.
This tool creates a new resource (a game app) on the TapTap platform, which is a reversible write operation. It does not execute arbitrary code, delete data, or involve financial transactions. The severity is medium because creation of unwanted apps could clutter a user's account or be used for spam/malicious distribution, but the action is reversible.
From the tool's definition Tool name 'tap_create_app' and description 'user wants to create a new game on TapTap platform' indicate creation of new data (a game application) on an external platform.
Attacks that exploit this kind of access
user wants to create a new game on 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_create_app accepts 3 parameters: genre, appName, developerId. 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_create_app: 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_create_app 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_create_app 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_create_app. 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_create_app 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 →