ecommerce.amazon.deals
Browse current Amazon deals — original price vs deal price, product title, ASIN, deal link. Paginated, 500+ active deals. 12 Amazon marketplaces (Canopy API)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/ecommerce.amazon.deals.md
What ecommerce.amazon.deals does on Apibase
AI agents call ecommerce.amazon.deals to retrieve information from Apibase without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
page | integer | — | Page number (default 1) |
domain | string | — | Amazon marketplace: US, UK, CA, DE, FR, IT, ES, AU, IN, MX, BR, JP (default US) |
Parameters from the server's own tool schema.
Why ecommerce.amazon.deals is rated Low
Retrieves public Amazon marketplace deal information with no side effects or data modification.
From the tool's definition Browse current Amazon deals, product title, ASIN, deal link. Paginated.
Attacks that exploit this kind of access
The rule that runs ecommerce.amazon.deals safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For ecommerce.amazon.deals, this is the rule to start with:
ecommerce.amazon.deals is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Apibase, apply this rule, and every ecommerce.amazon.deals call is checked against it from then on.
Questions about ecommerce.amazon.deals
Browse current Amazon deals — original price vs deal price, product title, ASIN, deal link. Paginated, 500+ active deals. 12 Amazon marketplaces (Canopy API). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
ecommerce.amazon.deals accepts 2 parameters: page, domain. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for ecommerce.amazon.deals: 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 Apibase. Nothing to install.
ecommerce.amazon.deals 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 ecommerce.amazon.deals 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 ecommerce.amazon.deals. 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.
ecommerce.amazon.deals is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue