# find_products Answer 'best under $N' and 'which has the most ' directly: filter a category by maxPriceUsd and/or brand, then rank by a field — 'priceUsd' (default, cheapest first), 'releaseDate', or any of the category's spec keys (set descending:true for biggest-first, e.g. sortBy:'battery_mah' descending:true). Returns provenanced product records; products missing the sort value sort last. Never infers a spec it has not verified. Agent View of the PolicyLayer registry record for `find_products`. HTML page: https://policylayer.com/tools/com-frontdeskreview-front-desk-review-data/find-products ## Facts - Tool: `find_products` - Server: The Front Desk Review (`https://mcp.frontdeskreview.com/mcp`) — https://policylayer.com/tools/com-frontdeskreview-front-desk-review-data.md - Homepage: https://github.com/AlexandDunk/frontdesk-data - Risk category: Read (Low risk) - Registry record: grade F, identity unverified - Server auth posture: open - Server rate-limited: no - Parameters: 5 (1 required) - Recommended policy verdict: Allowed ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `brand` | string | no | Only products from this brand. | | `sortBy` | string | no | Field to rank by: 'priceUsd' (default), 'releaseDate', or a spec key from the category. | | `category` | string | yes | Product category slug from list_product_categories. | | `descending` | boolean | no | Rank largest/newest first (default false = smallest/cheapest first). | | `maxPriceUsd` | number | no | Only products at or below this USD price. | 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": "find_products", "arguments": { "category": "" } } } ``` ## Why find_products is rated Low find_products is a search and ranking tool that retrieves and queries product data without modifying, deleting, or executing any operations. It performs filtering and sorting on existing product records, which are classic Read category operations. The low severity reflects that misuse would at worst return incorrect product recommendations with no side effects. From the tool's own definition: "Tool description states it 'filter[s] a category' and 'rank[s]' products, 'Returns provenanced product records'. The verbs are retrieval-focused: filter, rank, return. No mutations, deletions, executions, or financial operations are mentioned." ## Use case AI agents call find_products to retrieve information from The Front Desk Review 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 The Front Desk Review: ```json { "version": "1", "default": "deny", "tools": { "find_products": {} } } ``` ## Other tools on The Front Desk Review (18) - `compare` — Read — https://policylayer.com/tools/com-frontdeskreview-front-desk-review-data/compare.md - `compare_products` — Read — https://policylayer.com/tools/com-frontdeskreview-front-desk-review-data/compare-products.md - `find_best` — Read — https://policylayer.com/tools/com-frontdeskreview-front-desk-review-data/find-best.md - `get_benchmark` — Read — https://policylayer.com/tools/com-frontdeskreview-front-desk-review-data/get-benchmark.md - `get_cost_decoder` — Read — https://policylayer.com/tools/com-frontdeskreview-front-desk-review-data/get-cost-decoder.md - `get_independent_test_coverage` — Read — https://policylayer.com/tools/com-frontdeskreview-front-desk-review-data/get-independent-test-coverage.md - `get_normalized_pricing` — Read — https://policylayer.com/tools/com-frontdeskreview-front-desk-review-data/get-normalized-pricing.md - `get_price_history` — Read — https://policylayer.com/tools/com-frontdeskreview-front-desk-review-data/get-price-history.md - `list_cost_decoders` — Read — https://policylayer.com/tools/com-frontdeskreview-front-desk-review-data/list-cost-decoders.md - `list_coverage` — Read — https://policylayer.com/tools/com-frontdeskreview-front-desk-review-data/list-coverage.md - `list_product_categories` — Read — https://policylayer.com/tools/com-frontdeskreview-front-desk-review-data/list-product-categories.md - `list_sections` — Read — https://policylayer.com/tools/com-frontdeskreview-front-desk-review-data/list-sections.md - `most_volatile_in_category` — Read — https://policylayer.com/tools/com-frontdeskreview-front-desk-review-data/most-volatile-in-category.md - `price_movers` — Read — https://policylayer.com/tools/com-frontdeskreview-front-desk-review-data/price-movers.md - `search_products` — Read — https://policylayer.com/tools/com-frontdeskreview-front-desk-review-data/search-products.md - `search_vendors` — Read — https://policylayer.com/tools/com-frontdeskreview-front-desk-review-data/search-vendors.md - `volatility_for_entity` — Read — https://policylayer.com/tools/com-frontdeskreview-front-desk-review-data/volatility-for-entity.md - `whats_changed` — Read — https://policylayer.com/tools/com-frontdeskreview-front-desk-review-data/whats-changed.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-frontdeskreview-front-desk-review-data · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/com-frontdeskreview-front-desk-review-data