get_range
Get a daily time-series of exchange rates over a date range (business days). Capped at 366 rows per call; use next_cursor for pagination. Indicative developer-grade reference rates (aggregated market data + public reference rates), not for settlement or trading.
This record as markdown: /tools/dev-exchangerate-mcp/get-range.md
What get_range does on Exchangerate Dev
AI agents call get_range 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 | Description |
|---|---|---|---|
base | string | Yes | |
symbols | string | Yes | |
end_date | string | Yes | |
start_date | string | Yes |
Parameters from the server's own tool schema.
Why get_range is rated Low
This tool queries and retrieves historical FX rate data without side effects. The explicit disclaimer that rates are 'not for settlement or trading' reinforces that it cannot commit financial transactions. The capped pagination (366 rows max with next_cursor) is a Read pattern. No irreversible state changes, code execution, or financial operations are possible. Lowest severity category applies.
From the tool's definition get_range retrieves historical time-series exchange rate data with explicit pagination support. Description states it returns 'daily time-series of exchange rates' capped at 366 rows, indicating data retrieval only.
Attacks that exploit this kind of access
The rule that runs get_range 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_range, this is the rule to start with:
get_range 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 Exchangerate Dev, apply this rule, and every get_range call is checked against it from then on.
Questions about get_range
Get a daily time-series of exchange rates over a date range (business days). Capped at 366 rows per call; use next_cursor for pagination. Indicative developer-grade reference rates (aggregated market data + public reference rates), not for settlement or trading. It is categorised as a Read tool in the Exchangerate Dev MCP Server, which means it retrieves data without modifying state.
get_range accepts 4 parameters: base, symbols, end_date, start_date. Required: base, symbols, end_date, start_date. The full parameter table on this page comes from the server's own tool schema.
Register the Exchangerate Dev MCP server in PolicyLayer and add a rule for get_range: 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.
get_range 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 get_range 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 get_range. 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.
get_range 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.
More on Exchangerate Dev, and thousands of servers like it.
This server
Across the catalogue