AI agents call get_product_detail 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 | Product ID from search results |
Parameters from the server's own tool schema.
This tool retrieves and queries product data (images, pricing, landing pages, Shopify metadata) without creating, modifying, or deleting anything. It is a straightforward data retrieval operation with no side effects. The mention of credit consumption is consistent with a read-only API query model.
From the tool's definition Tool description states 'Get product detail including images, price, landing page, Shopify data' — purely retrieves product information with no modification or deletion capability. The credit system indicates a query/lookup operation.
Attacks that exploit this kind of access
Get product detail including images, price, landing page, Shopify data. 1 credit (free if queried within 3 days). It is categorised as a Read tool in the Pipiads MCP Server, which means it retrieves data without modifying state.
get_product_detail 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_product_detail: 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_product_detail 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_product_detail 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_product_detail. 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_product_detail 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 →