# convert

Convert an amount from one currency to another at the current rate. Indicative developer-grade reference rates (aggregated market data + public reference rates), not for settlement or trading.

Agent View of the PolicyLayer registry record for `convert`. HTML page: https://policylayer.com/tools/dev-exchangerate-mcp/convert

## Facts

- Tool: `convert`
- Server: Exchangerate Dev (`https://api.exchangerate.dev/v1/mcp/`) — https://policylayer.com/tools/dev-exchangerate-mcp.md
- Homepage: https://github.com/https://api.exchangerate.dev/v1/mcp/
- Risk category: Read (Low risk)
- Registry record: grade C, identity unverified
- Server auth posture: open
- Server rate-limited: yes
- Parameters: 3 (3 required)
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `to` | string | yes |  |
| `from` | string | yes |  |
| `amount` | object | yes |  |

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "convert",
    "arguments": {
      "to": "<to>",
      "from": "<from>",
      "amount": {}
    }
  }
}
```

## Why convert is rated Low

The tool performs a read-only currency conversion calculation using current exchange rates. It explicitly states it is indicative/reference only and not for settlement or trading, meaning it moves no money and has no financial side effects. It simply retrieves and computes a converted value.

From the tool's own definition: "Convert an amount from one currency to another at the current rate... not for settlement or trading."

## Use case

AI agents call convert to retrieve information from Exchangerate Dev without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Exchangerate Dev:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "convert": {}
  }
}
```

## Other tools on Exchangerate Dev (4)

- `get_range` — Read — https://policylayer.com/tools/dev-exchangerate-mcp/get-range.md
- `get_rate` — Read — https://policylayer.com/tools/dev-exchangerate-mcp/get-rate.md
- `list_currencies` — Read — https://policylayer.com/tools/dev-exchangerate-mcp/list-currencies.md
- `search_docs` — Read — https://policylayer.com/tools/dev-exchangerate-mcp/search-docs.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=dev-exchangerate-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/dev-exchangerate-mcp