AI agents call get_monitor_ad_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 |
ad_content | string | — | Ad content keyword |
ad_cost_end | number | — | Maximum ad cost |
landing_page | string | — | Landing page URL filter |
ad_cost_start | number | — | Minimum ad cost |
ad_status_list | array | — | Ad status filter |
active_days_end | number | — | Maximum active days |
ad_ended_at_end | number | — | Ad end time end |
Parameters from the server's own tool schema.
This tool retrieves or queries ad list data associated with a monitor task. The verb 'get' and the absence of any language suggesting modification, deletion, or execution means this is a read-only operation. The extensive filters suggest it queries/searches existing data. No side effects or state changes are implied.
From the tool's definition Tool name 'get_monitor_ad_list' and description 'Get ad list for a monitor task with extensive filters' indicate retrieval of existing monitoring data with no modification capability.
Risk signalsHigh parameter count (29 properties)
Attacks that exploit this kind of access
Get ad list for a monitor task with extensive filters. It is categorised as a Read tool in the Pipiads MCP Server, which means it retrieves data without modifying state.
get_monitor_ad_list accepts 12 parameters: page, keyword, task_id, order_by, per_page, ad_content, ad_cost_end, landing_page, ad_cost_start, ad_status_list, active_days_end, ad_ended_at_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_ad_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_ad_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_ad_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_ad_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_ad_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 →