AI agents call search_stores 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: 3=All, 4=Yesterday, 0=7d, 1=30d, 2=90d |
cpa_max | number | — | Maximum CPA |
cpa_min | number | — | Minimum CPA |
cpm_max | number | — | Maximum CPM |
cpm_min | number | — | Minimum CPM |
keyword | string | — | Search keyword |
ad_state | number | — | Ad state: 1=Active, 0=Stopped |
data_type | number | Yes | Platform: 0=All, 1=TikTok, 2=Facebook, 3=Meta Library |
page_size | integer | Yes | Results per page |
reach_max | number | — | Maximum Meta reach |
reach_min | number | — | Minimum Meta reach |
Parameters from the server's own tool schema.
This tool queries and retrieves store ranking data based on provided filters. It has no capability to modify data, execute code, delete records, or trigger financial transactions. The operation is purely informational and read-only, making it a low-severity Read category tool.
From the tool's definition Tool description states 'Search store ranking list' with filtering capabilities (platform, region, ad metrics, monthly visits).
Risk signalsHigh parameter count (36 properties)
Attacks that exploit this kind of access
Search store ranking list. Filter by platform, region, ad metrics, monthly visits. It is categorised as a Read tool in the Pipiads MCP Server, which means it retrieves data without modifying state.
search_stores accepts 12 parameters: sort, time, cpa_max, cpa_min, cpm_max, cpm_min, keyword, ad_state, data_type, page_size, reach_max, reach_min. Required: sort, time, data_type, page_size. 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_stores: 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_stores 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_stores 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_stores. 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_stores 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 →