get_historical
Return daily OHLCV bar history for a symbol. History depth is set automatically by your API key's plan — do NOT pass a tier argument (there is none): Free sees the last 30 days; Basic sees the last year; Pro unlocks full history back to 1996 (XAU/USD). Dates must be ISO 8601 (YYYY-MM-DD). Returns...
This record as markdown: /tools/dev-goldprice-mcp/get-historical.md
What get_historical does on Goldprice Dev
AI agents call get_historical 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 |
|---|---|---|---|
limit | integer | — | |
symbol | string | Yes | |
to_date | string | Yes | |
from_date | string | Yes |
Parameters from the server's own tool schema.
Why get_historical is rated Low
This is a pure data retrieval function that queries historical pricing information. It retrieves time-series data for gold, silver, copper commodities with no ability to modify data, execute code, or perform financial transactions. The tool is read-only with minimal blast radius if misused—an AI might retrieve unwanted historical data but cannot cause harm beyond information disclosure.
From the tool's definition Tool returns historical OHLCV bar data; description states 'Return daily OHLCV bar history' with no modification, deletion, or execution capabilities. Parameters are read-only (symbol, dates in ISO 8601 format). No side effects or state changes.
Attacks that exploit this kind of access
The rule that runs get_historical 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_historical, this is the rule to start with:
get_historical 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_historical call is checked against it from then on.
Questions about get_historical
Return daily OHLCV bar history for a symbol. History depth is set automatically by your API key's plan — do NOT pass a tier argument (there is none): Free sees the last 30 days; Basic sees the last year; Pro unlocks full history back to 1996 (XAU/USD). Dates must be ISO 8601 (YYYY-MM-DD). Returns bars in date-descending order. volume is null for spot instruments (XAU/USD, XAG/USD); real for futures (GC, SI, HG) and ETFs (GLD). It is categorised as a Read tool in the Goldprice Dev MCP Server, which means it retrieves data without modifying state.
get_historical accepts 4 parameters: limit, symbol, to_date, from_date. Required: symbol, to_date, from_date. 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_historical: 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_historical 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_historical 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_historical. 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_historical 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