get_series_history
PAID ($0.005). Historical values of a reference series with effective date ranges, optionally filtered by from/to (YYYY-MM-DD). Pass api_key if you have one; otherwise the response explains how to pay via x402.
This record as markdown: /tools/dev-asiaref-reference-data/get-series-history.md
What get_series_history does on Reference Data
AI agents call get_series_history to retrieve information from Reference Data 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 |
|---|---|---|---|
to | string | — | Latest effective date, YYYY-MM-DD |
from | string | — | Earliest effective date, YYYY-MM-DD |
series | string | Yes | Series id |
api_key | string | — | API key |
country | string | Yes | ISO country code |
Parameters from the server's own tool schema.
Why get_series_history is rated Low
Even though get_series_history 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.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs get_series_history safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Reference Data, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_series_history, this is the rule to start with:
get_series_history 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 Reference Data, apply this rule, and every get_series_history call is checked against it from then on.
Questions about get_series_history
PAID ($0.005). Historical values of a reference series with effective date ranges, optionally filtered by from/to (YYYY-MM-DD). Pass api_key if you have one; otherwise the response explains how to pay via x402. It is categorised as a Read tool in the Reference Data MCP Server, which means it retrieves data without modifying state.
get_series_history accepts 5 parameters: to, from, series, api_key, country. Required: series, country. The full parameter table on this page comes from the server's own tool schema.
Register the Reference Data MCP server in PolicyLayer and add a rule for get_series_history: 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 Reference Data. Nothing to install.
get_series_history 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_series_history 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_series_history. 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_series_history is provided by the Reference Data MCP server (https://asiaref.dev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Reference Data, and thousands of servers like it.
This server
Across the catalogue