AI agents call get_store_product_analysis 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 |
end_time | number | — | End time (unix timestamp) |
start_time | number | — | Start time (unix timestamp) |
Parameters from the server's own tool schema.
This tool retrieves or queries product analysis information from a store, which is a data retrieval operation with no indication of modification, deletion, code execution, or financial transaction. The context of the PipiAds advertising intelligence API suggests this accesses analytical data about products. There are no side effects implied, placing it squarely in the Read category with low severity.
From the tool's definition Tool name 'get_store_product_analysis' and description 'Get store product analysis' indicate a retrieval operation that queries existing product analysis data. The verb 'get' is characteristic of Read operations that retrieve data without side effects.
Attacks that exploit this kind of access
Get store product analysis. It is categorised as a Read tool in the Pipiads MCP Server, which means it retrieves data without modifying state.
get_store_product_analysis accepts 3 parameters: id, end_time, start_time. 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_product_analysis: 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_product_analysis 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_product_analysis 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_product_analysis. 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_product_analysis 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.
get_store_product_analysis is one line of Pipiads's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →