# search_products

Search the Filtrous catalog by free text and/or spec terms (e.g. '0.22 micron PES syringe filter'). Returns matching products with title, handle, SKU, product_type, tags, price, and availability. Open tool — no API key required.

Agent View of the PolicyLayer registry record for `search_products`. HTML page: https://policylayer.com/tools/com-filtrous-mcp-catalog/search-products

## Facts

- Tool: `search_products`
- Server: Filtrous MCP Catalog Server (`https://filtrous-mcp-catalog.filtrous.workers.dev/mcp`) — https://policylayer.com/tools/com-filtrous-mcp-catalog.md
- Homepage: https://github.com/https://filtrous-mcp-catalog.filtrous.workers.dev/mcp
- Risk category: Read (Low risk)
- Registry record: grade C, identity unverified
- Server auth posture: open
- Server rate-limited: no
- Parameters: 2 (1 required)
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `limit` | integer | no | Max results (default 10). |
| `query` | string | yes | Free-text and/or spec search. Field filters like 'product_type:...' or 'tag:...' are also honored. |

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "search_products",
    "arguments": {
      "query": "<query>"
    }
  }
}
```

## Why search_products is rated Low

search_products is a catalog query that retrieves product information without creating, modifying, deleting, or executing any operations. The ability to search and view product specifications, pricing, and availability is a read-only data retrieval function with no side effects or blast radius if an AI agent misuses it.

From the tool's own definition: "Tool 'searches' the catalog and 'returns matching products' — retrieves product data with no modification capability."

## Use case

AI agents call search_products to retrieve information from Filtrous MCP Catalog Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Filtrous MCP Catalog Server:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "search_products": {}
  }
}
```

## Other tools on Filtrous MCP Catalog Server (3)

- `get_price_and_lead_time` — Read — https://policylayer.com/tools/com-filtrous-mcp-catalog/get-price-and-lead-time.md
- `get_product_details` — Read — https://policylayer.com/tools/com-filtrous-mcp-catalog/get-product-details.md
- `request_quote` — Write — https://policylayer.com/tools/com-filtrous-mcp-catalog/request-quote.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=com-filtrous-mcp-catalog · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/com-filtrous-mcp-catalog