AI agents call gumroad_list_sales to retrieve information from UnClick without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
page | number | — | Page number for pagination |
after | string | — | Sales after this date (YYYY-MM-DD) |
email | string | — | Filter by buyer email |
before | string | — | Sales before this date (YYYY-MM-DD) |
api_key | string | Yes | Gumroad access token |
product_id | string | — | Filter by product ID |
Parameters from the server's own tool schema.
This tool queries and retrieves existing sales records from a Gumroad account without creating, modifying, or deleting data. It is a straightforward data retrieval operation with no side effects beyond returning filtered results. The filters (product, email, date range) are query parameters, not actions that trigger external operations.
From the tool's definition Tool name 'gumroad_list_sales' and description 'List sales from a Gumroad account. Filter by product, email, or date range.' indicate retrieval of sales data with filtering options. The verb 'list' and lack of modification language confirm read-only semantics.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
List sales from a Gumroad account. Filter by product, email, or date range. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
gumroad_list_sales accepts 6 parameters: page, after, email, before, api_key, product_id. Required: api_key. 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 gumroad_list_sales: 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.
gumroad_list_sales 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 gumroad_list_sales 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 gumroad_list_sales. 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.
gumroad_list_sales 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.
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 →