Get historical exchange rates for a currency pair.
AI agents call get_historical_rate to retrieve information from Currency Exchange without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical financial data without side effects. It does not create, modify, delete, or execute any operations. The low severity reflects minimal blast radius — an agent querying historical rates cannot cause financial harm, data loss, or unintended operations. The high confidence reflects clear, unambiguous read-only semantics.
From the tool's definition Tool name is 'get_historical_rate' and description states 'Get historical exchange rates for a currency pair' — a pure data retrieval operation with no modification, deletion, or execution of commands.
Attacks that exploit this kind of access
Get historical exchange rates for a currency pair. It is categorised as a Read tool in the Currency Exchange MCP Server, which means it retrieves data without modifying state.
Register the Currency Exchange MCP server in PolicyLayer and add a rule for get_historical_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 Currency Exchange. Nothing to install.
get_historical_rate 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_historical_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.
Set action: deny in the PolicyLayer policy for get_historical_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.
get_historical_rate is provided by the Currency Exchange MCP server (ruddxxy/currency-exchange-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →