AI agents call get_new_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 |
|---|---|---|---|
type | number | Yes | Type: 1=24h, 2=3d, 3=7d, 0=Default |
region | string | — | Country/region |
sort_key | string | Yes | "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" |
found_time | number | Yes | Discovery time: 1=3d, 2=7d, 3=1m, 4=3m, 5=6m, 6=All, 0=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 retrieves and queries advertising intelligence data about product rankings. It performs no modifications, deletions, code execution, or financial operations. The verb 'Get' and the read-only nature of ranking data classification places this firmly in the Read category with low severity.
From the tool's definition Tool name 'get_new_product_ranking' and description 'Get new ad product ranking list' indicate a retrieval operation with no side effects. The parameters (found_time, sort_key, sort_type, type) are query filters, not mutation or execution indicators.
Risk signalsHigh parameter count (13 properties)
Attacks that exploit this kind of access
Get new ad product ranking list. Requires found_time, sort_key, sort_type, type. It is categorised as a Read tool in the Pipiads MCP Server, which means it retrieves data without modifying state.
get_new_product_ranking accepts 12 parameters: type, region, sort_key, page_size, plat_type, shop_type, sort_type, found_time, current_page, growth_rate_max, growth_rate_min, count_growth_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_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_new_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_new_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_new_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_new_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 →