get_physical_price
Return the latest per-country physical dealer/retail gold prices — real quotes from dealers, mints, and bullion benchmarks, NOT spot-derived arithmetic — with nullable premium_over_spot_bps per quote (null when live reference inputs are unavailable). country is an ISO 3166-1 alpha-2 code (e.g. ID...
This record as markdown: /tools/dev-goldprice-mcp/get-physical-price.md
What get_physical_price does on Goldprice Dev
AI agents call get_physical_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 |
|---|---|---|---|
country | string | Yes |
Parameters from the server's own tool schema.
Why get_physical_price is rated Low
Even though get_physical_price only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs get_physical_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_physical_price, this is the rule to start with:
get_physical_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_physical_price call is checked against it from then on.
Questions about get_physical_price
Return the latest per-country physical dealer/retail gold prices — real quotes from dealers, mints, and bullion benchmarks, NOT spot-derived arithmetic — with nullable premium_over_spot_bps per quote (null when live reference inputs are unavailable). country is an ISO 3166-1 alpha-2 code (e.g. ID, IN, AE, JP). Requires the Physical tier or higher; static sample responses for evaluation are in the docs at https://goldprice.dev/docs/physical. It is categorised as a Read tool in the Goldprice Dev MCP Server, which means it retrieves data without modifying state.
get_physical_price accepts 1 parameter: country. Required: country. 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_physical_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_physical_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_physical_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_physical_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_physical_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