square_catalog_search
Search Square catalog objects by text.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/square-catalog-search.md
What square_catalog_search does on UnClick
AI agents call square_catalog_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 |
|---|---|---|---|
limit | number | — | |
cursor | string | — | |
text_filter | string | Yes | Text to search for |
access_token | string | Yes | |
object_types | array | — | Types to search (default: ['ITEM']) |
Parameters from the server's own tool schema.
Why square_catalog_search is rated Low
This tool performs a read-only search operation on catalog data. It queries and retrieves information without creating, modifying, deleting, or executing anything. The search functionality is a classic Read operation with minimal security risk if misused by an AI agent.
From the tool's definition Tool is described as 'Search Square catalog objects by text' — a retrieval operation with no modification, deletion, or execution capability.
Risk signalsHandles credentials or secrets (access_token)
Attacks that exploit this kind of access
The rule that runs square_catalog_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 square_catalog_search, this is the rule to start with:
square_catalog_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 square_catalog_search call is checked against it from then on.
Questions about square_catalog_search
Search Square catalog objects by text. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
square_catalog_search accepts 5 parameters: limit, cursor, text_filter, access_token, object_types. Required: text_filter, 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_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.
square_catalog_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 square_catalog_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 square_catalog_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.
square_catalog_search 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