get_rate

SERVERExchangerate Dev SOURCEhttps://api.exchangerate.dev/v1/mcp/

Low RISK CLASS

Category Read

Parameters 32 required

Recommended Allowedsee the rule below

Registry record Grade C, identity unverified Pull the record →

This record as markdown: /tools/dev-exchangerate-mcp/get-rate.md

WHAT IT DOES

What get_rate does on Exchangerate Dev

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

Parameter	Type	Required
`base`	string	Yes
`date`	object	—
`quote`	string	Yes

Parameters from the server's own tool schema.

RISK

Why get_rate is rated Low

This tool performs a data retrieval operation only. It fetches historical or current exchange rate information but does not execute trades, modify data, or commit financial obligations. The disclaimer that rates are 'not for settlement or trading' further confirms this is informational only. While exchange rates have financial context, the tool itself only reads and returns data without any transactional capability.

From the tool's definition Tool retrieves exchange rate data without modification: 'Get the current — or historical, with date — exchange rate' with no capability to modify rates, execute transactions, or affect financial systems. Explicitly stated as 'not for settlement or trading'.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_rate safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Exchangerate Dev, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_rate, this is the rule to start with:

get_rate Allowed

get_rate is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_rate": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Exchangerate Dev, apply this rule, and every get_rate call is checked against it from then on.

FAQ

Questions about get_rate

What does the get_rate tool do? +

Get the current — or historical, with date — exchange rate from one currency to another. Indicative developer-grade reference rates (aggregated market data + public reference rates), not for settlement or trading. Rates update ~60s for real-time currencies through the trading week when the live overlay is active; the source field on every response is the authoritative freshness indicator (live | ecb_daily | fred_daily) — rates fall back to ECB or FRED daily reference during market closures, data-source unavailability, or low liquidity. market_session on every response indicates open, weekend, or interbank_closed. It is categorised as a Read tool in the Exchangerate Dev MCP Server, which means it retrieves data without modifying state.

What parameters does get_rate accept? +

get_rate accepts 3 parameters: base, date, quote. Required: base, quote. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_rate? +

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

What risk level is get_rate? +

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

Can I rate-limit get_rate? +

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

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

get_rate is provided by the Exchangerate Dev MCP server (https://api.exchangerate.dev/v1/mcp/). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Exchangerate Dev, and thousands of servers like it.

This server

All 5 Exchangerate Dev tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →