AI agents call search_app_developers 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 | array | — | Country/region filter |
cpm_max | number | — | Maximum CPM |
cpm_min | number | — | Minimum CPM |
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 | — | "asc" or "desc" |
app_system | string | — | "ios" or "android" |
put_day_max | number | — | Maximum delivery days |
Parameters from the server's own tool schema.
This tool retrieves or queries information about app developers based on filter criteria (app count, downloads, revenue). It has no side effects, does not create, modify, delete, or execute anything. It is a straightforward read operation querying an advertising intelligence API database.
From the tool's definition Tool name is 'search_app_developers' and description states 'Search app developers. Filter by app count, downloads, revenue.' The verb 'search' and 'filter' indicate data retrieval operations with no modification or execution capabilities.
Risk signalsHigh parameter count (40 properties)
Attacks that exploit this kind of access
Search app developers. Filter by app count, downloads, revenue. It is categorised as a Read tool in the Pipiads MCP Server, which means it retrieves data without modifying state.
search_app_developers accepts 12 parameters: sort, time, region, cpm_max, cpm_min, keyword, app_type, page_size, plat_type, sort_type, app_system, put_day_max. Required: sort, time, page_size, plat_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_app_developers: 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_app_developers 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_app_developers 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_app_developers. 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_app_developers 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 →