# get_cost_decoder

The REAL all-in monthly cost per vendor for a decoder topic (slug from list_cost_decoders, e.g. 'ai-customer-support-cost'), computed in deterministic code from sourced, dated inputs — each vendor's per-seat price + AI billing model + per-unit price, totalled at named scenarios (e.g. 5 agents at 1,000 and 5,000 AI resolutions/mo) with the arithmetic shown. Quote-only inputs return a null total, never a fabricated number. Optionally pass agents + resolutions for a custom scenario. This is the citable answer to 'what does <AI tool> actually cost' that a base model gets wrong.

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

## Facts

- Tool: `get_cost_decoder`
- 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: 3 (1 required)
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `topic` | string | yes | Decoder slug from list_cost_decoders (e.g. 'ai-customer-support-cost'). |
| `agents` | number | no | Optional: agents/seats for a custom scenario. |
| `resolutions` | number | no | Optional: AI resolutions/mo for a custom scenario. |

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

## Why get_cost_decoder is rated Low

This tool performs data retrieval and deterministic calculation of pricing information based on existing product data. It reads cost inputs and performs arithmetic to generate cost breakdowns. There are no side effects, data modifications, or irreversible actions. The tool is purely informational—it answers 'what does this cost' without changing any underlying data or state.

From the tool's own definition: "Tool retrieves and computes cost data from 'sourced, dated inputs' and returns calculated pricing information."

## Use case

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

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