AI agents call get_new_app_ranking to retrieve information from Pipiads without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
type | number | Yes | Type: 1=24h, 2=3d, 3=7d, 0=Default |
region | string | — | Country/region |
app_type | string | — | "game" or "app" |
sort_key | string | Yes | Sort field |
page_size | integer | Yes | Results per page |
plat_type | number | — | Platform: 0=All, 1=TikTok, 2=Facebook |
sort_type | string | Yes | "asc" or "desc" |
app_system | string | — | "ios" or "android" |
found_time | number | Yes | Discovery time filter |
app_category | string | — | App category |
current_page | integer | Yes | Page number |
growth_rate_max | number | — | Maximum growth rate |
Parameters from the server's own tool schema.
This tool retrieves or queries app ranking data without side effects. The use of 'get' and 'ranking list' confirms it is a read-only operation that does not create, modify, delete, or execute any code. No financial or destructive operations are involved.
From the tool's definition Tool name 'get_new_app_ranking' and description 'Get new apps ranking list' both indicate a retrieval operation with no modification of data.
Risk signalsHigh parameter count (16 properties)
Attacks that exploit this kind of access
Get new apps ranking list. It is categorised as a Read tool in the Pipiads MCP Server, which means it retrieves data without modifying state.
get_new_app_ranking accepts 12 parameters: type, region, app_type, sort_key, page_size, plat_type, sort_type, app_system, found_time, app_category, current_page, growth_rate_max. Required: type, sort_key, page_size, sort_type, found_time, current_page. The full parameter table on this page comes from the server's own tool schema.
Register the Pipiads MCP server in PolicyLayer and add a rule for get_new_app_ranking: 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 Pipiads. Nothing to install.
get_new_app_ranking 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 get_new_app_ranking 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 get_new_app_ranking. 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.
get_new_app_ranking is provided by the Pipiads MCP server (pipiads-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 →