# 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.

Agent View of the PolicyLayer registry record for `get_series_history`. HTML page: https://policylayer.com/tools/dev-euroref-reference-data/get-series-history

## Facts

- Tool: `get_series_history`
- Server: Reference Data (`https://euroref.dev/mcp`) — https://policylayer.com/tools/dev-euroref-reference-data.md
- Homepage: https://github.com/https://euroref.dev/mcp
- Risk category: Read (Low risk)
- Registry record: grade D, identity unverified
- Server auth posture: open
- Server rate-limited: no
- Parameters: 5 (2 required)
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `to` | string | no | Latest effective date, YYYY-MM-DD |
| `from` | string | no | Earliest effective date, YYYY-MM-DD |
| `series` | string | yes | Series id |
| `api_key` | string | no | API key |
| `country` | string | yes | ISO country code |

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_series_history",
    "arguments": {
      "series": "<series>",
      "country": "<country>"
    }
  }
}
```

## 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 signals: Handles credentials or secrets (api_key)

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Reference Data:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_series_history": {}
  }
}
```

## Other tools on Reference Data (9)

- `check_minimum_wage` — Read — https://policylayer.com/tools/dev-euroref-reference-data/check-minimum-wage.md
- `compute_income_tax` — Read — https://policylayer.com/tools/dev-euroref-reference-data/compute-income-tax.md
- `count_working_days` — Read — https://policylayer.com/tools/dev-euroref-reference-data/count-working-days.md
- `get_public_holidays` — Read — https://policylayer.com/tools/dev-euroref-reference-data/get-public-holidays.md
- `get_series` — Read — https://policylayer.com/tools/dev-euroref-reference-data/get-series.md
- `get_snapshot` — Read — https://policylayer.com/tools/dev-euroref-reference-data/get-snapshot.md
- `list_series` — Read — https://policylayer.com/tools/dev-euroref-reference-data/list-series.md
- `settlement_date` — Read — https://policylayer.com/tools/dev-euroref-reference-data/settlement-date.md
- `compute_vat` — Write — https://policylayer.com/tools/dev-euroref-reference-data/compute-vat.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-euroref-reference-data · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/dev-euroref-reference-data