norgesbank.fx.history
Retrieve a historical time series of official Norges Bank exchange rates for any of the 41 available currencies versus NOK. Specify a start/end date (ISO 8601, e.g. 2024-01-01) to get a custom range of business-day spot rates. Returns an array of {date, rate} pairs sorted ascending by date. Usefu...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/norgesbank.fx.history.md
What norgesbank.fx.history does on Apibase
AI agents call norgesbank.fx.history to retrieve information from Apibase 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 |
|---|---|---|---|
currency | string | Yes | ISO 4217 currency code for which to fetch historical rates against NOK (e.g. "USD", "EUR", "GBP"). |
end_date | string | — | End date of the historical range in ISO 8601 format (YYYY-MM-DD). Defaults to today if omitted. |
start_date | string | — | Start date of the historical range in ISO 8601 format (YYYY-MM-DD). Defaults to 30 days ago if omitted. |
Parameters from the server's own tool schema.
Why norgesbank.fx.history is rated Low
Purely retrieves historical exchange rate data with no side effects.
From the tool's definition Retrieve a historical time series of official Norges Bank exchange rates
Attacks that exploit this kind of access
The rule that runs norgesbank.fx.history safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For norgesbank.fx.history, this is the rule to start with:
norgesbank.fx.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 Apibase, apply this rule, and every norgesbank.fx.history call is checked against it from then on.
Questions about norgesbank.fx.history
Retrieve a historical time series of official Norges Bank exchange rates for any of the 41 available currencies versus NOK. Specify a start/end date (ISO 8601, e.g. 2024-01-01) to get a custom range of business-day spot rates. Returns an array of {date, rate} pairs sorted ascending by date. Useful for charting NOK strength, backtesting currency strategies, or computing historical hedging costs. Data: Norges Bank SDMX EXR dataflow, no auth. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
norgesbank.fx.history accepts 3 parameters: currency, end_date, start_date. Required: currency. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for norgesbank.fx.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 Apibase. Nothing to install.
norgesbank.fx.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 norgesbank.fx.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 norgesbank.fx.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.
norgesbank.fx.history is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue