currency.exchange.convert
Convert amount between any two currencies — 160+ currencies supported. Returns conversion rate and result (ExchangeRate-API)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/currency.exchange.convert.md
What currency.exchange.convert does on Apibase
AI agents call currency.exchange.convert to retrieve information from Apibase 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 |
|---|---|---|---|
to | string | Yes | Target currency code (e.g. "EUR") |
from | string | Yes | Source currency code (e.g. "USD") |
amount | number | — | Amount to convert (default 1) |
Parameters from the server's own tool schema.
Why currency.exchange.convert is rated Low
Retrieves exchange rates and performs calculation; no financial transaction or data modification occurs.
From the tool's definition Convert amount between currencies, returns conversion rate and result.
Attacks that exploit this kind of access
The rule that runs currency.exchange.convert safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For currency.exchange.convert, this is the rule to start with:
currency.exchange.convert 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 Apibase, apply this rule, and every currency.exchange.convert call is checked against it from then on.
Questions about currency.exchange.convert
Convert amount between any two currencies — 160+ currencies supported. Returns conversion rate and result (ExchangeRate-API). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
currency.exchange.convert accepts 3 parameters: to, from, amount. Required: to, from. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for currency.exchange.convert: 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 Apibase. Nothing to install.
currency.exchange.convert 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 currency.exchange.convert 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 currency.exchange.convert. 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.
currency.exchange.convert is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue