AI agents call get_store_play_cost 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 | Store ID |
type | number | — | Data type |
time_end | number | — | End time (unix timestamp) |
page_size | number | — | Results per page |
time_start | number | — | Start time (unix timestamp) |
current_page | number | — | Page number |
Parameters from the server's own tool schema.
This tool retrieves advertising performance metrics and cost statistics from the PipiAds API. It has no side effects—it only reads and returns data about ad spend and performance. No data is created, modified, deleted, or any external operations are triggered.
From the tool's definition Tool name 'get_store_play_cost' and description 'Get store play cost / daily ad increment statistics' indicate retrieval of advertising analytics data.
Attacks that exploit this kind of access
Get store play cost / daily ad increment statistics. It is categorised as a Read tool in the Pipiads MCP Server, which means it retrieves data without modifying state.
get_store_play_cost accepts 6 parameters: id, type, time_end, page_size, time_start, current_page. 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_store_play_cost: 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_store_play_cost 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_store_play_cost 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_store_play_cost. 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_store_play_cost 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 →