This record as markdown: /tools/creativelead-unclick/amazon-search.md
What amazon_search does on UnClick
AI agents call amazon_search to retrieve information from UnClick 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 |
|---|---|---|---|
region | string | — | |
keywords | string | — | |
itemCount | number | — | |
access_key | string | — | |
secret_key | string | — | |
partner_tag | string | — | |
searchIndex | string | — |
Parameters from the server's own tool schema.
Why amazon_search is rated Low
This tool performs a search query on Amazon's product catalog, which is a read-only operation. It retrieves information but does not create, modify, delete, or execute code. The blast radius of misuse is minimal—an attacker could perform unwanted searches but cannot access sensitive user data, make purchases, or cause financial harm through search operations alone.
From the tool's definition Tool name 'amazon_search' and description 'Search for products on Amazon' indicate a query operation that retrieves product data without modifying or deleting anything.
Attacks that exploit this kind of access
The rule that runs amazon_search safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For amazon_search, this is the rule to start with:
amazon_search 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 UnClick, apply this rule, and every amazon_search call is checked against it from then on.
Questions about amazon_search
Search for products on Amazon. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
amazon_search accepts 7 parameters: region, keywords, itemCount, access_key, secret_key, partner_tag, searchIndex. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for amazon_search: 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 UnClick. Nothing to install.
amazon_search 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 amazon_search 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 amazon_search. 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.
amazon_search is provided by the UnClick MCP server (creativelead/unclick). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue