AI agents call get_monitor_landing_page_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_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 |
first_ad_date_end | number | — | First ad date end |
recent_ad_date_end | number | — | Recent ad date end |
Parameters from the server's own tool schema.
This tool retrieves or queries monitoring data (landing page lists) without creating, modifying, deleting, or executing operations. It is a read-only data retrieval function, fitting the Read category with low severity since it poses minimal risk of misuse.
From the tool's definition Tool name and description indicate retrieval of existing data: 'Get landing page list' — a query operation with no modification, deletion, or execution of external actions.
Risk signalsHigh parameter count (16 properties)
Attacks that exploit this kind of access
Get landing page list for a monitor task. It is categorised as a Read tool in the Pipiads MCP Server, which means it retrieves data without modifying state.
get_monitor_landing_page_list accepts 12 parameters: page, keyword, task_id, order_by, per_page, direction, max_ad_days, min_ad_days, max_ad_count, min_ad_count, first_ad_date_end, recent_ad_date_end. 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_landing_page_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_landing_page_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_landing_page_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_landing_page_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_landing_page_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 →