# volatility_for_entity

How volatile ONE product or vendor's price has been: a 0-100 volatility score derived from its recorded moves (frequency × average move size), plus change count, net % and last change. Honest gate: below a minimum recorded-change threshold it returns sufficient:false with a note, never a score invented from a single point.

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

## Facts

- Tool: `volatility_for_entity`
- 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. |

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

## Why volatility_for_entity is rated Low

This tool queries existing price history data to compute and return volatility statistics. It performs no write, execution, deletion, or financial operations. The worst misuse scenario is an agent requesting volatility data to inform a decision, which poses minimal risk. Classified as Read with low severity.

From the tool's own definition: "Tool retrieves and analyzes historical price volatility data ('volatility score derived from its recorded moves', 'change count, net %', 'last change'). Returns calculated metrics and metadata with no modification of underlying data."

## Use case

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

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