New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

norgesbank.rates.history

Retrieve a historical time series of Norges Bank key policy interest rates. Choose rate type (SD = key policy rate, OL = overnight lending rate, RR = reserve rate), frequency (B = business daily, M = monthly, A = annual), and date range. Returns {date, rate} pairs sorted ascending. Useful for mon...

SERVERApibase SOURCEapibase-mcp-client
Low RISK CLASS
Category Read
Parameters 40 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-whiteknightonhorse-apibase/norgesbank.rates.history.md

What norgesbank.rates.history does on Apibase

AI agents call norgesbank.rates.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.

ParameterTypeRequiredDescription
end_date string — End date of the historical range in ISO 8601 format (YYYY-MM-DD or YYYY-MM). Defaults to today if omitted.
frequency string — Observation frequency: "B" = business daily (default), "M" = monthly average, "A" = annual average.
rate_type string — Type of key policy rate to retrieve: "SD" = key policy rate (deposit rate), "OL" = overnight lending rate, "RR" = reserve rate. Omit to get all three types.
start_date string — Start date of the historical range in ISO 8601 format (YYYY-MM-DD or YYYY-MM). Defaults to 1 year ago if omitted.

Parameters from the server's own tool schema.

Why norgesbank.rates.history is rated Low

Retrieves historical interest rate data with no side effects or irreversible actions.

From the tool's definition Retrieve a historical time series of Norges Bank key policy interest rates.

Questions about norgesbank.rates.history

What does the norgesbank.rates.history tool do? +

Retrieve a historical time series of Norges Bank key policy interest rates. Choose rate type (SD = key policy rate, OL = overnight lending rate, RR = reserve rate), frequency (B = business daily, M = monthly, A = annual), and date range. Returns {date, rate} pairs sorted ascending. Useful for monetary-policy research, macro models, or comparing Norway's rate cycle against other central banks. Data: Norges Bank SDMX IR dataflow, no auth. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.

What parameters does norgesbank.rates.history accept? +

norgesbank.rates.history accepts 4 parameters: end_date, frequency, rate_type, start_date. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on norgesbank.rates.history? +

Register the Apibase MCP server in PolicyLayer and add a rule for norgesbank.rates.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.

What risk level is norgesbank.rates.history? +

norgesbank.rates.history is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit norgesbank.rates.history? +

Yes. Add a rate_limit block to the norgesbank.rates.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.

How do I block norgesbank.rates.history completely? +

Set action: deny in the PolicyLayer policy for norgesbank.rates.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.

What MCP server provides norgesbank.rates.history? +

norgesbank.rates.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.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Apibase's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.