square_catalog_list
List Square catalog objects (items, categories, taxes, etc.).
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/square-catalog-list.md
What square_catalog_list does on UnClick
AI agents call square_catalog_list 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 | — | |
types | string | — | Comma-separated types (ITEM, CATEGORY, etc.) |
cursor | string | — | |
access_token | string | Yes |
Parameters from the server's own tool schema.
Why square_catalog_list is rated Low
This tool performs a read-only query of Square catalog data (items, categories, taxes, etc.). It retrieves and lists existing catalog objects without creating, modifying, deleting, or executing any side effects. The term 'list' is a classic Read operation indicator. Low severity because misuse would only expose catalog metadata, not enable financial transactions, deletions, or code execution.
From the tool's definition Tool name 'square_catalog_list' and description 'List Square catalog objects' indicate a retrieval operation with no modification of data.
Risk signalsHandles credentials or secrets (access_token)
Attacks that exploit this kind of access
The rule that runs square_catalog_list 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 square_catalog_list, this is the rule to start with:
square_catalog_list 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 square_catalog_list call is checked against it from then on.
Questions about square_catalog_list
List Square catalog objects (items, categories, taxes, etc.). It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
square_catalog_list accepts 4 parameters: limit, types, cursor, access_token. Required: access_token. 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 square_catalog_list: 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.
square_catalog_list 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 square_catalog_list 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 square_catalog_list. 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.
square_catalog_list 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