frankfurter-historical
Get ECB reference FX rates for a specific historical date.
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.
Attacks that exploit this kind of access
The rule that runs frankfurter-historical safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Meta Data Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For frankfurter-historical, this is the rule to start with:
frankfurter-historical 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 Meta Data Mcp, apply this rule, and every frankfurter-historical call is checked against it from then on.
Questions about frankfurter-historical
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.
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.
frankfurter-historical 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 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.
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.
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.
This server
Across the catalogue