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.
This record as markdown: /tools/dev-goldprice-mcp/get-metadata.md
What get_metadata does on Goldprice Dev
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.
| Parameter | Type | Required | Description |
|---|---|---|---|
symbol | string | Yes |
Parameters from the server's own tool schema.
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 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.
Attacks that exploit this kind of access
The rule that runs get_metadata 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_metadata, this is the rule to start with:
get_metadata 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_metadata call is checked against it from then on.
Questions about 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. It is categorised as a Read tool in the Goldprice Dev MCP Server, which means it retrieves data without modifying state.
get_metadata 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_metadata: 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_metadata 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_metadata 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_metadata. 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_metadata 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