frankfurter-historical

Get ECB reference FX rates for a specific historical date.

SERVERMeta Data Mcp SOURCEpypi:meta-data-mcp
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-derekslinz-meta-data-mcp/frankfurter-historical.md

What frankfurter-historical does on Meta Data Mcp

AI agents call frankfurter-historical to retrieve information from Meta Data Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why frankfurter-historical is rated Low

This tool queries public financial reference data (historical FX rates) without the ability to execute trades, move money, modify records, or trigger irreversible actions. It is purely informational retrieval of historical data from a public API. While it touches the financial domain, it does not commit financial obligations or execute transactions—merely read-access to historical rates.

From the tool's definition Tool retrieves historical FX rates from ECB (European Central Bank) reference data. The verb 'Get' and domain of querying historical exchange rate data indicates read-only retrieval with no modification or side effects.

Questions about frankfurter-historical

What does the frankfurter-historical tool do? +

Get ECB reference FX rates for a specific historical date. It is categorised as a Read tool in the Meta Data Mcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on frankfurter-historical? +

Register the Meta Data MCP server in PolicyLayer and add a rule for frankfurter-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 Meta Data Mcp. Nothing to install.

What risk level is frankfurter-historical? +

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

Can I rate-limit frankfurter-historical? +

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

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

frankfurter-historical is provided by the Meta Data MCP server (pypi:meta-data-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Meta Data, 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 Meta Data'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.