Low Risk

get_historical_rates

get_historical_rates

How to control get_historical_rates ↓

AI agents call get_historical_rates to retrieve information from Currency Converter MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

This tool retrieves historical exchange rate data from the Frankfurter API. It is a read-only operation that queries and returns data without creating, modifying, deleting, or executing any operations. The empty description slightly reduces confidence, but the name and server context clearly indicate a data retrieval function.

From the tool's definition Tool name 'get_historical_rates' and server description indicating it 'fetch[es]... historical rates' and 'list available currencies' — purely data retrieval with no modification or side effects.

Documented attack patterns abuse exactly the kind of access get_historical_rates gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Currency Converter MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get_historical_rates:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_historical_rates": {}
  }
}

get_historical_rates is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Currency Converter MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the get_historical_rates tool do? +

get_historical_rates. It is categorised as a Read tool in the Currency Converter MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_historical_rates? +

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

What risk level is get_historical_rates? +

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

Can I rate-limit get_historical_rates? +

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

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

get_historical_rates is provided by the Currency Converter MCP server (wesbos/currency-conversion-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Currency Converter MCP tool call.

Deterministic rules across all 4 Currency Converter MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4 Currency Converter MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.