exchangerate_historical
Get historical exchange rates for a specific date. Requires an API key.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/exchangerate-historical.md
What exchangerate_historical does on UnClick
AI agents call exchangerate_historical to retrieve information from UnClick 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 |
|---|---|---|---|
day | string | Yes | Day number (1-31) |
base | string | — | Base currency code (default USD) |
year | string | Yes | 4-digit year |
month | string | Yes | Month number (1-12) |
api_key | string | — | ExchangeRate-API key (required) |
Parameters from the server's own tool schema.
Why exchangerate_historical is rated Low
This tool retrieves historical financial data (exchange rates) but does not execute trades, move money, modify data, or trigger irreversible actions. It is purely informational and read-only, making it a Read category tool with low severity—misuse would only result in data retrieval, not financial loss or system damage.
From the tool's definition Tool name 'exchangerate_historical' and description 'Get historical exchange rates for a specific date' indicate a query/retrieval operation with no side effects.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs exchangerate_historical safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For exchangerate_historical, this is the rule to start with:
exchangerate_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 UnClick, apply this rule, and every exchangerate_historical call is checked against it from then on.
Questions about exchangerate_historical
Get historical exchange rates for a specific date. Requires an API key. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
exchangerate_historical accepts 5 parameters: day, base, year, month, api_key. Required: day, year, month. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for exchangerate_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 UnClick. Nothing to install.
exchangerate_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 exchangerate_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 exchangerate_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.
exchangerate_historical is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue