AI agents call get_monitor_product_list 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 |
|---|---|---|---|
page | number | — | Page number |
keyword | string | — | Search keyword |
task_id | string | Yes | Monitor task ID |
order_by | string | — | Sort field |
per_page | number | — | Results per page |
direction | string | — | "asc" or "desc" |
max_price | number | — | Maximum price |
min_price | number | — | Minimum price |
max_ad_days | number | — | Maximum ad days |
min_ad_days | number | — | Minimum ad days |
max_ad_count | number | — | Maximum ad count |
min_ad_count | number | — | Minimum ad count |
Parameters from the server's own tool schema.
This tool retrieves or queries a list of ad products associated with a monitor task, applying filters as needed. There are no side effects, data modifications, deletions, or external operations triggered. It is a straightforward read operation that returns existing data without changing system state.
From the tool's definition Tool name 'get_monitor_product_list' and description 'Get ad product list for a monitor task with filters' indicate data retrieval with optional filtering. The 'Get' verb and 'list' retrieval pattern are characteristic of read operations.
Risk signalsHigh parameter count (20 properties)
Attacks that exploit this kind of access
Get ad product list for a monitor task with filters. It is categorised as a Read tool in the Pipiads MCP Server, which means it retrieves data without modifying state.
get_monitor_product_list accepts 12 parameters: page, keyword, task_id, order_by, per_page, direction, max_price, min_price, max_ad_days, min_ad_days, max_ad_count, min_ad_count. Required: task_id. 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_monitor_product_list: 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_monitor_product_list 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_monitor_product_list 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_monitor_product_list. 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_monitor_product_list 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 →