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-forma...
This record as markdown: /tools/dev-goldprice-mcp/get-carat.md
What get_carat does on Goldprice Dev
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.
| Parameter | Type | Required | Description |
|---|---|---|---|
currency | string | — |
Parameters from the server's own tool schema.
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 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 signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs get_carat safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Goldprice Dev, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_carat, this is the rule to start with:
get_carat is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Goldprice Dev, apply this rule, and every get_carat call is checked against it from then on.
Questions about 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). It is categorised as a Read tool in the Goldprice Dev MCP Server, which means it retrieves data without modifying state.
get_carat accepts 1 parameter: currency. The full parameter table on this page comes from the server's own tool schema.
Register the Goldprice Dev MCP server in PolicyLayer and add a rule for get_carat: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Goldprice Dev. Nothing to install.
get_carat is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_carat rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for get_carat. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
get_carat is provided by the Goldprice Dev MCP server (https://api.goldprice.dev/v1/mcp/). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Goldprice Dev, and thousands of servers like it.
This server
Across the catalogue