# price_movers

Recorded price MOVES across the index within a recency window (default 90 days), newest-and-largest first — each a dated before→after change of a tracked entity. Optionally filter by kind ('hw'/'sw') or category/theme slug. The freshness a base model structurally cannot have. Returns an empty list with a clear note when nothing moved in the window (a quiet window is honestly quiet).

Agent View of the PolicyLayer registry record for `price_movers`. HTML page: https://policylayer.com/tools/com-frontdeskreview-front-desk-review-data/price-movers

## Facts

- Tool: `price_movers`
- 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: 4
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `kind` | string | no | Limit to 'hw' (hardware product) or 'sw' (software vendor). Omit to match either; a slug is resolved across both. |
| `limit` | integer | no | Max movers to return (default 25). |
| `category` | string | no | Limit to one category/theme slug (e.g. '3d-printers', 'ai-receptionists'). |
| `withinDays` | integer | no | Recency window in days (default 90), measured against the log's latest date. |

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": "price_movers",
    "arguments": {}
  }
}
```

## Why price_movers is rated Low

Tool retrieves historical price movement data with no side effects.

From the tool's own definition: "Recorded price MOVES... returns dated before→after change"

## Use case

AI agents call price_movers 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": {
    "price_movers": {}
  }
}
```

## 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_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
- `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