AI agents call get_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 |
|---|---|---|---|
time | number | Yes | Time filter |
type | number | Yes | Type: 1=Day, 2=Week, 3=Month, 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" |
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 performs a read-only query to retrieve app ranking information. It has no side effects, does not modify data, execute code, delete records, or involve financial transactions. The blast radius of misuse is minimal—an agent could only retrieve publicly available or authorized ranking data.
From the tool's definition Tool name 'get_app_ranking' and description 'Get top apps ranking list' indicate a retrieval operation that queries and returns ranking data without modifying or executing external operations.
Risk signalsHigh parameter count (23 properties)
Attacks that exploit this kind of access
Get top apps ranking list. It is categorised as a Read tool in the Pipiads MCP Server, which means it retrieves data without modifying state.
get_app_ranking accepts 12 parameters: time, type, region, app_type, sort_key, page_size, plat_type, sort_type, app_system, app_category, current_page, growth_rate_max. Required: time, type, sort_key, page_size, sort_type, 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_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_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_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_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_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 →