exchangerate_convert
Convert an amount from one currency to another.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/exchangerate-convert.md
What exchangerate_convert does on UnClick
AI agents use exchangerate_convert to create or update resources in UnClick, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your UnClick environment.
| 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) |
api_key | string | — | Optional for conversion (uses latest rates if omitted) |
Parameters from the server's own tool schema.
Why exchangerate_convert is rated Medium
An AI agent can call exchangerate_convert faster than any human can review: one bad instruction and it creates or modifies resources in UnClick by the hundred, each call as confident as the last.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs exchangerate_convert 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_convert, this is the rule to start with:
exchangerate_convert stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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_convert call is checked against it from then on.
Questions about exchangerate_convert
Convert an amount from one currency to another. It is categorised as a Write tool in the UnClick MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
exchangerate_convert accepts 4 parameters: to, from, amount, api_key. Required: to, from. 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_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 UnClick. Nothing to install.
exchangerate_convert is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the exchangerate_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 exchangerate_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.
exchangerate_convert 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