# get_independent_test_coverage The independent-testing provenance for ONE product (by category + slug) — a COUNT of evidence, never a quality score. Fields: outlets (independent outlets on record), labs (how many physically tested it and left >=1 measured value), metrics (distinct kinds of metric measured, with names), mentioned (outlets that only mentioned it), and a ready-to-quote reading sentence. Use it to state how much independent hands-on evidence backs any claim about a product. A low count means little independent evidence has been gathered yet, NOT that the product is bad; a high count means well-documented, NOT better. Returns found:false (never a fabricated count) for an unknown or unreviewed product. Agent View of the PolicyLayer registry record for `get_independent_test_coverage`. HTML page: https://policylayer.com/tools/com-frontdeskreview-front-desk-review-data/get-independent-test-coverage ## Facts - Tool: `get_independent_test_coverage` - 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: 2 (2 required) - Recommended policy verdict: Allowed ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `slug` | string | yes | Product slug (e.g. 'dji-osmo-action-5-pro'). | | `category` | string | yes | Product category slug (e.g. 'action-cameras', '3d-printers'). | 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": "get_independent_test_coverage", "arguments": { "slug": "", "category": "" } } } ``` ## Why get_independent_test_coverage is rated Low This tool purely queries and retrieves metadata about product test coverage and evidence counts. It performs no side effects, data modification, code execution, or deletion. The tool returns read-only information about testing provenance with no capability to alter, destroy, or create data. It is a straightforward data retrieval operation. From the tool's own definition: "Tool retrieves 'independent-testing provenance for ONE product' and returns 'a COUNT of evidence' with fields like 'outlets', 'labs', 'metrics', and 'mentioned'." ## Use case AI agents call get_independent_test_coverage 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": { "get_independent_test_coverage": {} } } ``` ## 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 - `find_products` — Read — https://policylayer.com/tools/com-frontdeskreview-front-desk-review-data/find-products.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_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