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...
This record as markdown: /tools/dev-asiaref-reference-data/settlement-date.md
What settlement_date does on Reference Data
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.
| Parameter | Type | Required | Description |
|---|---|---|---|
market | string | — | ISO country of the market whose cited cycle should apply (with instrument_class) |
api_key | string | — | 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 | — | The offset you are trading under (T+n) |
instrument_class | string | — | Instrument class — a government bond never inherits an equity cycle |
Parameters from the server's own tool schema.
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 signalsHandles credentials or secrets (api_key) · Bulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs settlement_date 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 settlement_date, this is the rule to start with:
settlement_date 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 settlement_date call is checked against it from then on.
Questions about 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. It is categorised as a Read tool in the Reference Data MCP Server, which means it retrieves data without modifying state.
settlement_date accepts 6 parameters: market, api_key, calendars, trade_date, business_days, instrument_class. Required: calendars, trade_date. 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 settlement_date: 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.
settlement_date 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 settlement_date 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 settlement_date. 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.
settlement_date 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