# get_price_history

The full dated price series for ONE product or vendor (by slug), plus derived stats: first-tracked date, current/low/high, number of recorded changes, net % since tracked, the largest single move, and the last change. This is the citable answer to 'how much did X cost', 'did X's price drop', and price-trend questions — grounded on a real, append-only series, not a model's guess. Returns found:false (never a fabricated series) for an unknown slug.

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

## Facts

- Tool: `get_price_history`
- 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 (1 required)
- 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. |
| `slug` | string | yes | Product or vendor slug (e.g. 'bambu-lab-a1', 'goodcall'). |

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

## Why get_price_history is rated Low

This tool is a pure data retrieval mechanism that queries historical pricing information with no side effects. It does not create, modify, delete, or execute operations—it only reads and aggregates existing price data. The low severity reflects minimal risk: misuse would yield only informational artifacts, not data corruption, financial transactions, or arbitrary code execution.

From the tool's own definition: "The tool description explicitly states it 'retrieves' a 'full dated price series' and returns 'derived stats' for a product."

## Use case

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

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