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

getHistoricalInterestRates

Returns the published history of a benchmark rate over an optional date range, given as start_date/end_date (YYYY-MM-DD) or start_time/end_time (UNIX seconds). For the latest value only use /interestrate.

SERVERAPI Ninjas SOURCEhttps://mcp.api-ninjas.com/mcp
Low RISK CLASS
Category Read
Parameters 61 required
Recommended Allowedsee the rule below
Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/com-api-ninjas-mcp/gethistoricalinterestrates.md

What getHistoricalInterestRates does on API Ninjas

AI agents call getHistoricalInterestRates to retrieve information from API Ninjas without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

ParameterTypeRequiredDescription
page string — Pagination cursor. Pass the `next` value from a previous response to retrieve the following page of data points.
rate string Yes The specific interest rate identifier. Supports central bank rates (e.g. central_bank_us, central_bank_eu), benchmark rates (e.g. sofr, effr, euribor_3_months,
end_date string — End date for the data range (inclusive) in YYYY-MM-DD format, UTC. Cannot be combined with end_time.
end_time integer — End time for the data range, specified as a UNIX timestamp in seconds. Alternative to end_date.
start_date string — Start date for the data range (inclusive) in YYYY-MM-DD format, UTC. Cannot be combined with start_time.
start_time integer — Start time for the data range, specified as a UNIX timestamp in seconds. Alternative to start_date.

Parameters from the server's own tool schema.

Why getHistoricalInterestRates is rated Low

Even though getHistoricalInterestRates 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.

Questions about getHistoricalInterestRates

What does the getHistoricalInterestRates tool do? +

Returns the published history of a benchmark rate over an optional date range, given as start_date/end_date (YYYY-MM-DD) or start_time/end_time (UNIX seconds). For the latest value only use /interestrate. It is categorised as a Read tool in the API Ninjas MCP Server, which means it retrieves data without modifying state.

What parameters does getHistoricalInterestRates accept? +

getHistoricalInterestRates accepts 6 parameters: page, rate, end_date, end_time, start_date, start_time. Required: rate. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on getHistoricalInterestRates? +

Register the API Ninjas MCP server in PolicyLayer and add a rule for getHistoricalInterestRates: 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 API Ninjas. Nothing to install.

What risk level is getHistoricalInterestRates? +

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

Can I rate-limit getHistoricalInterestRates? +

Yes. Add a rate_limit block to the getHistoricalInterestRates 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 getHistoricalInterestRates completely? +

Set action: deny in the PolicyLayer policy for getHistoricalInterestRates. 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 getHistoricalInterestRates? +

getHistoricalInterestRates is provided by the API Ninjas MCP server (https://mcp.api-ninjas.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on API Ninjas, 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 API Ninjas'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.