Low Risk

search-catalog

Search for products on any UCP-enabled Shopify store. Searches the store's live product catalog via UCP/MCP and returns matching products with titles, prices, variants, and images. Examples: - domain: "allbirds.com", query: "tree topper" - domain: "gymshark.com", query: ...

Accepts freeform code/query input (query)

Part of the UCP Checker MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

ucpchecker/ucp-checker Read Risk 2/5

AI agents call search-catalog to retrieve information from UCP Checker without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though search-catalog only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

ucpchecker-ucp-checker.yaml
tools:
  search-catalog:
    rules:
      - action: allow

See the full UCP Checker policy for all 10 tools.

Tool Name search-catalog
Category Read
Risk Level Low

View all 10 tools →

Agents calling read-class tools like search-catalog have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

What does the search-catalog tool do? +

Search for products on any UCP-enabled Shopify store. Searches the store's live product catalog via UCP/MCP and returns matching products with titles, prices, variants, and images. Examples: - domain: "allbirds.com", query: "tree topper" - domain: "gymshark.com", query: "hoodie". It is categorised as a Read tool in the UCP Checker MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search-catalog? +

Add a rule in your Intercept YAML policy under the tools section for search-catalog. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the UCP Checker MCP server.

What risk level is search-catalog? +

search-catalog is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit search-catalog? +

Yes. Add a rate_limit block to the search-catalog rule in your Intercept 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.

How do I block search-catalog completely? +

Set action: deny in the Intercept policy for search-catalog. 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.

What MCP server provides search-catalog? +

search-catalog is provided by the UCP Checker MCP server (ucpchecker/ucp-checker). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on UCP Checker

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.