# settlement_date

PAID ($0.05). Settlement/value date: the date n business days after a trade date, computed on the INTERSECTION of the calendars you name, with a per-day trail showing every skipped day and why, on which calendar. Supply business_days for a cycle you are trading under, or market + instrument_class to have a settlement cycle applied that we cite to its primary source (e.g. US equities T+1 under 17 CFR 240.15c6-1(a); UK gilts T+1 by DMO convention, which is NOT the T+2 equity cycle; Japan equities T+2 but JGBs T+1). Calendars are NATIONAL statutory holiday calendars with researched statutory weekend rules (Israel Saturday-only, Gulf Friday+Saturday, India Sundays plus the 2nd and 4th Saturday), NOT CSD or exchange calendars — each response states the basis and any known divergence. Use 'eu.t2' for the euro cash leg. We refuse FREE rather than guess: beyond published calendar coverage, no cited cycle for the instrument (government bonds never inherit an equity cycle), a cycle not in force on the trade date, or FX spot value dates. Free companion: GET /settlement-conventions.

Agent View of the PolicyLayer registry record for `settlement_date`. HTML page: https://policylayer.com/tools/dev-asiaref-reference-data/settlement-date

## Facts

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

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `market` | string | no | ISO country of the market whose cited cycle should apply (with instrument_class) |
| `api_key` | string | no | API key (bypasses x402; metered for invoicing) |
| `calendars` | array | yes | Calendar ids to intersect: two-letter ISO country codes, plus 'eu.t2' for the euro cash leg |
| `trade_date` | string | yes | Trade/reference date, YYYY-MM-DD. Day 0: never counted, never rolled. |
| `business_days` | integer | no | The offset you are trading under (T+n) |
| `instrument_class` | string | no | Instrument class — a government bond never inherits an equity cycle |

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": "settlement_date",
    "arguments": {
      "calendars": [],
      "trade_date": "<trade_date>"
    }
  }
}
```

## Why settlement_date is rated Low

Even though settlement_date 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) · Bulk/mass operation — affects multiple targets

## Use case

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

## Other tools on Reference Data (9)

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