AI agents call list_monitor_tasks 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 |
country | string | — | Country filter |
keyword | string | — | Search keyword |
order_by | string | — | Sort field |
per_page | number | — | Results per page |
direction | string | — | "asc" or "desc" |
monitor_task_type | number | — | Task type filter |
Parameters from the server's own tool schema.
This tool retrieves and queries existing ad monitoring task data. It performs a read-only operation that does not create, modify, delete, or execute any external operations. The optional filters are query parameters for narrowing results, not for altering data.
From the tool's definition Tool is named 'list_monitor_tasks' and described as 'List all ad monitoring tasks with optional filters.' The verb 'list' and action of retrieving/querying existing monitoring tasks indicates data retrieval with no side effects.
Attacks that exploit this kind of access
List all ad monitoring tasks with optional filters. It is categorised as a Read tool in the Pipiads MCP Server, which means it retrieves data without modifying state.
list_monitor_tasks accepts 7 parameters: page, country, keyword, order_by, per_page, direction, monitor_task_type. 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 list_monitor_tasks: 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.
list_monitor_tasks 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 list_monitor_tasks 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 list_monitor_tasks. 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.
list_monitor_tasks 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 →