AI agents call get_product_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 |
sort_key | string | Yes | Sort field: "count_growth", "growth_rate", "video_count" |
page_size | integer | Yes | Results per page |
plat_type | number | — | Platform: 0=All, 1=TikTok, 2=Facebook |
shop_type | string | — | E-commerce system |
sort_type | string | Yes | "asc", "desc", or "default" |
current_page | integer | Yes | Page number |
growth_rate_max | number | — | Maximum growth rate |
growth_rate_min | number | — | Minimum growth rate |
count_growth_max | number | — | Maximum growth count |
Parameters from the server's own tool schema.
This tool queries and returns ranking data from the PipiAds advertising intelligence API. It accepts filter/sort parameters but does not create, modify, delete, execute code, or commit financial transactions. The action is purely informational retrieval, classifying it as Read category with low severity.
From the tool's definition Tool retrieves 'ad product ranking list' with filtering parameters (sort_key, sort_type, time, type). The verb 'Get' and the retrieval nature indicate data querying with no modification or side effects.
Risk signalsHigh parameter count (13 properties)
Attacks that exploit this kind of access
Get ad product ranking list. Requires sort_key, sort_type, time, type. It is categorised as a Read tool in the Pipiads MCP Server, which means it retrieves data without modifying state.
get_product_ranking accepts 12 parameters: time, type, region, sort_key, page_size, plat_type, shop_type, sort_type, current_page, growth_rate_max, growth_rate_min, count_growth_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_product_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_product_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_product_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_product_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_product_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 →