AI agents call get_monitor_product_stats 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 |
|---|---|---|---|
task_id | string | Yes | Monitor task ID |
date_end | number | — | Date end |
date_start | number | — | Date start |
Parameters from the server's own tool schema.
This tool queries and returns advertising intelligence data (product statistics for a monitoring task). It performs no creation, modification, deletion, or execution of external operations. The impact of misuse is limited to unauthorized access to advertising intelligence data, which presents a low security risk in terms of blast radius.
From the tool's definition Tool name and description indicate retrieval of statistics: 'Get active ad product statistics for a monitor task.' The verb 'Get' and the read-only nature of fetching existing statistics confirm this is a data retrieval operation with no side effects.
Attacks that exploit this kind of access
Get active ad product statistics 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_product_stats accepts 3 parameters: task_id, date_end, date_start. 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_stats: 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_stats 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_stats 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_stats. 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_stats 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 →