get_spot_price
Return the latest aggregated spot (or GC futures) price for one symbol. Price is a Decimal-formatted string; is_stale is true when aggregator detected source divergence or stale FX.
This record as markdown: /tools/dev-goldprice-mcp/get-spot-price.md
What get_spot_price does on Goldprice Dev
AI agents call get_spot_price 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 |
|---|---|---|---|
symbol | string | Yes |
Parameters from the server's own tool schema.
Why get_spot_price is rated Low
This tool queries and retrieves current commodity price information. It performs a read-only lookup of spot prices and futures data without creating, modifying, deleting, or executing any operations. The 'is_stale' flag is informational metadata, not a side effect. No financial transactions, code execution, or data modifications occur.
From the tool's definition Tool description states it 'Return[s] the latest aggregated spot (or GC futures) price' — a retrieval operation with no modification or side effects. The output is price data and staleness metadata.
Attacks that exploit this kind of access
The rule that runs get_spot_price 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_spot_price, this is the rule to start with:
get_spot_price 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_spot_price call is checked against it from then on.
Questions about get_spot_price
Return the latest aggregated spot (or GC futures) price for one symbol. Price is a Decimal-formatted string; is_stale is true when aggregator detected source divergence or stale FX. It is categorised as a Read tool in the Goldprice Dev MCP Server, which means it retrieves data without modifying state.
get_spot_price accepts 1 parameter: symbol. Required: symbol. 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_spot_price: 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_spot_price 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_spot_price 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_spot_price. 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_spot_price 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