AI agents call get_monitor_ad_detail 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 |
|---|---|---|---|
ad_id | string | Yes | Ad ID |
Parameters from the server's own tool schema.
This tool retrieves advertising intelligence data about a specific ad using its ID. It performs a read-only query with no side effects, no data modification, and no triggering of external operations. The narrow scope (querying a single ad detail from an already-created monitor task) and passive nature of the operation place it firmly in the Read category with low severity.
From the tool's definition Tool description states 'Get ad detail from a monitor task by ad ID' — a retrieval operation with no modification, deletion, or execution of external systems.
Attacks that exploit this kind of access
Get ad detail from a monitor task by ad ID. It is categorised as a Read tool in the Pipiads MCP Server, which means it retrieves data without modifying state.
get_monitor_ad_detail accepts 1 parameter: ad_id. Required: ad_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_detail: 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_detail 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_detail 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_detail. 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_detail 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 →