etsy_get_shop_listings
Get active listings for an Etsy shop.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/etsy-get-shop-listings.md
What etsy_get_shop_listings does on UnClick
AI agents call etsy_get_shop_listings 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 |
|---|---|---|---|
limit | number | — | |
offset | number | — | |
api_key | string | Yes | |
shop_id | string | Yes | |
sort_on | string | — | |
sort_order | string | — |
Parameters from the server's own tool schema.
Why etsy_get_shop_listings is rated Low
This tool retrieves information about Etsy shop listings—a read-only, query operation with no side effects. It does not create, modify, delete, or execute actions. The blast radius of misuse is minimal since it only exposes already-public shop listing information.
From the tool's definition Tool name 'etsy_get_shop_listings' and description 'Get active listings for an Etsy shop' indicate a retrieval operation that queries and returns publicly available shop data without modification.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs etsy_get_shop_listings 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 etsy_get_shop_listings, this is the rule to start with:
etsy_get_shop_listings 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 etsy_get_shop_listings call is checked against it from then on.
Questions about etsy_get_shop_listings
Get active listings for an Etsy shop. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
etsy_get_shop_listings accepts 6 parameters: limit, offset, api_key, shop_id, sort_on, sort_order. Required: api_key, shop_id. 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 etsy_get_shop_listings: 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.
etsy_get_shop_listings 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 etsy_get_shop_listings 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 etsy_get_shop_listings. 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.
etsy_get_shop_listings is provided by the UnClick MCP server (@unclick/mcp-server). 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