AI agents call get_advertiser_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 |
|---|---|---|---|
id | string | Yes | Advertiser unique identifier ID |
Parameters from the server's own tool schema.
This tool queries and returns information about an advertiser without creating, modifying, deleting, or executing any operations. It is a straightforward data retrieval function typical of API intelligence platforms, posing minimal risk even if misused by an AI agent, as it only exposes existing advertiser metadata.
From the tool's definition Tool retrieves advertiser details (domain, ad count, products, region distribution) by ID with no indication of modification or side effects.
Attacks that exploit this kind of access
Get advertiser detail by ID. Returns domain, ad count, products, region distribution. It is categorised as a Read tool in the Pipiads MCP Server, which means it retrieves data without modifying state.
get_advertiser_detail accepts 1 parameter: id. Required: 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_advertiser_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_advertiser_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_advertiser_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_advertiser_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_advertiser_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 →