forex_historical
Get historical forex rates from Open Exchange Rates.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/forex-historical.md
What forex_historical does on UnClick
AI agents call forex_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 |
|---|---|---|---|
base | string | — | |
date | string | Yes | |
api_key | string | — |
Parameters from the server's own tool schema.
Why forex_historical is rated Low
This tool retrieves historical currency exchange rate data from an external API (Open Exchange Rates). It performs a query operation with no side effects—it neither modifies data, executes commands, deletes information, nor commits financial transactions.
From the tool's definition Tool description states 'Get historical forex rates' - a retrieval operation with no modification capability. The verb 'Get' and the focus on querying historical data indicates a read-only operation.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs forex_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 forex_historical, this is the rule to start with:
forex_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 forex_historical call is checked against it from then on.
Questions about forex_historical
Get historical forex rates from Open Exchange Rates. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
forex_historical accepts 3 parameters: base, date, api_key. Required: date. 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 forex_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.
forex_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 forex_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 forex_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.
forex_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