AI agents call ai_search_image_ads 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 |
|---|---|---|---|
sort | number | — | Sort field |
region | array | — | Country/region filter |
image_id | string | Yes | Image ID from submit response |
page_size | number | — | Results per page |
plat_type | number | — | Platform: 1=TikTok, 2=Facebook |
sort_type | string | — | "asc" or "desc" |
put_day_max | number | — | Maximum delivery days |
put_day_min | number | — | Minimum delivery days |
current_page | number | — | Page number |
digg_count_max | number | — | Maximum like count |
digg_count_min | number | — | Minimum like count |
play_count_max | number | — | Maximum play count |
Parameters from the server's own tool schema.
This tool performs an informational search against an advertising database to find similar ads. It retrieves or queries data (search) with no permanent modifications, code execution, deletions, or financial impact. The search operation is read-only with minimal blast radius if misused—an agent could only retrieve unwanted advertising information, not modify systems or commit financial obligations.
From the tool's definition Tool name 'ai_search_image_ads' and description 'Search ads similar to a submitted image' indicate a query/search operation that retrieves advertising data without modifying, executing commands, or causing side effects.
Risk signalsHigh parameter count (15 properties)
Attacks that exploit this kind of access
Search ads similar to a submitted image. It is categorised as a Read tool in the Pipiads MCP Server, which means it retrieves data without modifying state.
ai_search_image_ads accepts 12 parameters: sort, region, image_id, page_size, plat_type, sort_type, put_day_max, put_day_min, current_page, digg_count_max, digg_count_min, play_count_max. Required: image_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 ai_search_image_ads: 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.
ai_search_image_ads 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 ai_search_image_ads 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 ai_search_image_ads. 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.
ai_search_image_ads 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 →