# get_carat

Return per-gram gold (XAU) prices by karat purity — 24k, 22k, 21k, 20k, 18k, 16k, 14k, 10k — in a requested currency (default USD; the same 31 currencies get_spot_price serves). Jewelry-grade pricing computed from live XAU spot + ECB FX. FREE on every tier — no plan gate. Values are Decimal-formatted strings, quantized to the currency's ISO 4217 minor unit (JPY → whole numbers, USD → 2dp).

Agent View of the PolicyLayer registry record for `get_carat`. HTML page: https://policylayer.com/tools/dev-goldprice-mcp/get-carat

## Facts

- Tool: `get_carat`
- Server: Goldprice Dev (`https://api.goldprice.dev/v1/mcp/`) — https://policylayer.com/tools/dev-goldprice-mcp.md
- Homepage: https://github.com/https://api.goldprice.dev/v1/mcp/
- Risk category: Read (Low risk)
- Registry record: grade C, identity unverified
- Server auth posture: open
- Server rate-limited: yes
- Parameters: 1
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `currency` | string | no |  |

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

## Why get_carat is rated Low

This is a pure data retrieval tool. It queries and returns gold prices in various purities and currencies. There are no side effects, no state changes, no code execution, and no financial transactions—it simply reads and computes pricing information from existing data sources.

From the tool's own definition: "Tool 'Return[s]...prices' — retrieves/queries gold pricing data by karat purity without modifying any data. Description emphasizes 'Return' and 'computed from live XAU spot + ECB FX', indicating read-only data aggregation."

Risk signals: Bulk/mass operation — affects multiple targets

## Use case

AI agents call get_carat to retrieve information from Goldprice Dev 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 Goldprice Dev:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_carat": {}
  }
}
```

## Other tools on Goldprice Dev (7)

- `get_forward_view` — Read — https://policylayer.com/tools/dev-goldprice-mcp/get-forward-view.md
- `get_historical` — Read — https://policylayer.com/tools/dev-goldprice-mcp/get-historical.md
- `get_metadata` — Read — https://policylayer.com/tools/dev-goldprice-mcp/get-metadata.md
- `get_physical_price` — Read — https://policylayer.com/tools/dev-goldprice-mcp/get-physical-price.md
- `get_spot_price` — Read — https://policylayer.com/tools/dev-goldprice-mcp/get-spot-price.md
- `list_commodities` — Read — https://policylayer.com/tools/dev-goldprice-mcp/list-commodities.md
- `search_docs` — Read — https://policylayer.com/tools/dev-goldprice-mcp/search-docs.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=dev-goldprice-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/dev-goldprice-mcp