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

frankfurter.currency.historical

Retrieve ECB reference exchange rates for a specific historical date from Frankfurter.dev. Coverage starts from 1999-01-04 (Euro launch). If the requested date falls on a weekend or ECB holiday, the preceding business day is returned. Supports optional base currency, target currency filter, and a...

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

This record as markdown: /tools/io-github-whiteknightonhorse-apibase/frankfurter.currency.historical.md

What frankfurter.currency.historical does on Apibase

AI agents call frankfurter.currency.historical 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
base string — Base currency ISO 4217 code (default: EUR). Supported: AUD,BRL,CAD,CHF,CNY,CZK,DKK,EUR,GBP,HKD,HUF,IDR,ILS,INR,ISK,JPY,KRW,MXN,MYR,NOK,NZD,PHP,PLN,RON,SEK,SGD,T
date string Yes Historical date in YYYY-MM-DD format. ECB data available from 1999-01-04. Weekends/holidays return the preceding business day.
amount number — Amount to convert (default: 1.0).
symbols string — Comma-separated target currency codes (e.g. USD,GBP). Omit for all 33 currencies.

Parameters from the server's own tool schema.

Why frankfurter.currency.historical is rated Low

Tool retrieves historical currency exchange data with no side effects or modifications.

From the tool's definition Retrieve ECB reference exchange rates for a specific historical date

Questions about frankfurter.currency.historical

What does the frankfurter.currency.historical tool do? +

Retrieve ECB reference exchange rates for a specific historical date from Frankfurter.dev. Coverage starts from 1999-01-04 (Euro launch). If the requested date falls on a weekend or ECB holiday, the preceding business day is returned. Supports optional base currency, target currency filter, and amount scaling. Returns 33 major currencies: AUD, BRL, CAD, CHF, CNY, CZK, DKK, GBP, HKD, HUF, IDR, ILS, INR, ISK, JPY, KRW, MXN, MYR, NOK, NZD, PHP, PLN, RON, SEK, SGD, THB, TRY, USD, ZAR and more. No auth required; public domain ECB data. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.

What parameters does frankfurter.currency.historical accept? +

frankfurter.currency.historical accepts 4 parameters: base, date, amount, symbols. Required: date. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on frankfurter.currency.historical? +

Register the Apibase MCP server in PolicyLayer and add a rule for frankfurter.currency.historical: 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 frankfurter.currency.historical? +

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

Can I rate-limit frankfurter.currency.historical? +

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

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

frankfurter.currency.historical 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.