AI agents call get_store_rank_data 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 |
Parameters from the server's own tool schema.
This tool retrieves existing store traffic ranking information. It is a read operation that queries data without side effects, making it a Read category tool. The severity is low because accessing ranking data poses minimal risk—it does not modify systems, execute code, delete data, or involve financial transactions.
From the tool's definition Tool name is 'get_store_rank_data' and description states 'Get store traffic ranking data.' The verb 'Get' and action of retrieving ranking data indicate a read-only query operation with no data modification, creation, or deletion.
Attacks that exploit this kind of access
Get store traffic ranking data. It is categorised as a Read tool in the Pipiads MCP Server, which means it retrieves data without modifying state.
get_store_rank_data accepts 1 parameter: id. 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_rank_data: 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_rank_data 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_rank_data 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_rank_data. 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_rank_data 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 →