AI agents call search_apps 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 | Yes | Sort field |
time | number | Yes | Time range |
region | string | — | Country/region |
keyword | string | — | Search keyword |
app_type | string | — | "game" or "app" |
page_size | integer | Yes | Results per page |
plat_type | number | Yes | Platform: 0=All, 1=TikTok, 2=Facebook |
sort_type | string | Yes | "asc" or "desc" |
app_system | string | — | "ios" or "android" |
put_day_max | number | — | Maximum delivery days |
put_day_min | number | — | Minimum delivery days |
search_type | number | Yes | Search type |
Parameters from the server's own tool schema.
This tool queries the PipiAds API to retrieve information about advertised apps. It performs a read-only search operation with filters but does not create, modify, delete, or execute any operations. No side effects beyond data retrieval are possible. The sibling tools (ai_search_image_*, ai_search_image_tiktok_*) follow the same read-only pattern, reinforcing this classification.
From the tool's definition Tool is described as 'Search apps' with filtering capabilities (category, system, downloads, revenue). The verb 'search' and filtering parameters indicate data retrieval with no modification or execution capability.
Risk signalsHigh parameter count (38 properties)
Attacks that exploit this kind of access
Search apps advertised on TikTok/Facebook. Filter by category, system, downloads, revenue. It is categorised as a Read tool in the Pipiads MCP Server, which means it retrieves data without modifying state.
search_apps accepts 12 parameters: sort, time, region, keyword, app_type, page_size, plat_type, sort_type, app_system, put_day_max, put_day_min, search_type. Required: sort, time, page_size, plat_type, sort_type, search_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 search_apps: 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.
search_apps 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 search_apps 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 search_apps. 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.
search_apps 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 →