AI agents call tap_get_app_status 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 |
|---|---|---|---|
appId | number | — | The app id of the game |
Parameters from the server's own tool schema.
This tool queries and returns the status of an existing app using its ID. It is a read-only operation with no creation, modification, deletion, or financial implications. Misuse risk is low as it only exposes app status information.
From the tool's definition 'get the app status' and 'directly use the app_id' — retrieves status information for an app by ID, no side effects mentioned
Attacks that exploit this kind of access
user wants to get the app status, directly use the app_id. It is categorised as a Read tool in the Tds MCP Server, which means it retrieves data without modifying state.
tap_get_app_status accepts 1 parameter: appId. 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_get_app_status: 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_get_app_status 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_get_app_status 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_get_app_status. 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_get_app_status 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 →