This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/ls-list-customers.md
What ls_list_customers does on UnClick
AI agents call ls_list_customers 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 |
|---|---|---|---|
page | number | — | |
email | string | — | |
api_key | string | — | |
per_page | number | — | |
store_id | string | — |
Parameters from the server's own tool schema.
Why ls_list_customers is rated Low
This tool retrieves customer information from a Lemon Squeezy e-commerce store. It performs no mutation, deletion, or external state change. While the data retrieved may be sensitive (customer information), the tool itself only reads and does not modify or destroy data. Classification is Read with low severity since exposure would allow data exfiltration but not irreversible harm or financial transactions.
From the tool's definition Tool name 'ls_list_customers' and description 'List customers for a Lemon Squeezy store' indicate a query/retrieval operation. The verb 'list' is a classic Read operation that retrieves existing customer data without modification or side effects.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs ls_list_customers 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 ls_list_customers, this is the rule to start with:
ls_list_customers 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 ls_list_customers call is checked against it from then on.
Questions about ls_list_customers
List customers for a Lemon Squeezy store. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
ls_list_customers accepts 5 parameters: page, email, api_key, per_page, store_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 ls_list_customers: 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.
ls_list_customers 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 ls_list_customers 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 ls_list_customers. 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.
ls_list_customers 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