// SCAN REPORT

Exchangerate Dev

5 tools. 0 can modify or destroy data without limits.

Read-only server. Low risk, but rate limits prevent runaway API costs.

Last updated: 18 Aug 2026

0 can modify or destroy data

5 read-only

5 tools total

Community server · catalogue entry checked 18/08/2026 · full schemas captured for 4 of 5 tools

How to control Exchangerate Dev ↓

TOOL MAP

What Exchangerate Dev exposes to your agents

Read (5) Write / Execute (0) Destructive / Financial (0)

Running more than one server? Check your whole stack →

CONTEXT-WINDOW COST

What Exchangerate Dev costs in tokens

603 tokens of tool definitions, loaded on every request

0.3% of a 200k context window

182 heaviest tool: get_rate

Full per-tool breakdown → Model it in the token calculator →

THE RISK

What can go wrong

Even read-only tools carry cost. An agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up bills.

POLICY

How to control Exchangerate Dev

PolicyLayer is an MCP gateway — it sits between your AI agents and Exchangerate Dev, and nothing reaches the server without passing your rules. These are the rules we recommend:

Cap read operations

{
  "convert": {
    "limits": [
      {
        "counter": "convert_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Exchangerate Dev — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON EXCHANGERATE DEV →

Instant setup, no code required.

FULL CATALOGUE

All 5 Exchangerate Dev tools

READ 5 tools

Read convert Convert an amount from one currency to another at the current rate. Indicative developer-grade reference rates Read get_range Get a daily time-series of exchange rates over a date range (business days). Capped at 366 rows per call; when Read get_rate Get the current — or historical, with date — exchange rate from one currency to another. Indicative developer- Read list_currencies List all supported currencies with name, decimal precision, minor units, and whether the pair is derived (tria Read search_docs Search the exchangerate.dev FAQ corpus via BM25. Returns the top-K matching questions and answers with relevan

FAQ

Questions about Exchangerate Dev

Is the Exchangerate Dev MCP server safe to use without restrictions? +

The Exchangerate Dev server is primarily read-only with 5 read tools. While it cannot modify data, an agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up costs. Rate limiting is still recommended.

How many tools does the Exchangerate Dev MCP server expose? +

5 tools across 2 categories: Read, Write. 5 are read-only. 0 can modify, create, or delete data.

How do I enforce a policy on Exchangerate Dev? +

Register the Exchangerate Dev MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Exchangerate Dev tool call.

Deterministic rules across all 5 Exchangerate Dev tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON EXCHANGERATE DEV →

Instant setup, no code required.

5 Exchangerate Dev tools catalogued and risk-classified — across an index of 46,500+ MCP servers.

// WHERE THIS COMES FROM

These policies come from Exchangerate Dev's registry record.

The record behind this page: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →