# get_metadata

Return provenance metadata for a symbol: aggregated sources, unit, methodology URL, staleness rules. Use for attribution and to document data lineage in downstream reports.

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

## Facts

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

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `symbol` | string | yes |  |

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

## Why get_metadata is rated Low

This tool retrieves metadata about data sources and lineage for financial instruments (gold/silver/copper prices). It queries and returns informational attributes only—sources, units, methodology references, and staleness rules. There are no side effects, no data modification, no code execution, and no financial transactions. It is purely a Read operation used for documentation and attribution purposes.

From the tool's own definition: "Tool description states it 'Return[s] provenance metadata for a symbol: aggregated sources, unit, methodology URL, staleness rules.' This is a retrieval operation with no modification or execution capability."

## Use case

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

## Other tools on Goldprice Dev (7)

- `get_carat` — Read — https://policylayer.com/tools/dev-goldprice-mcp/get-carat.md
- `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_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