# search_docs

Search the exchangerate.dev FAQ corpus via BM25. Returns the top-K matching questions and answers with relevance scores. Use before answering how-to / pricing / data-sourcing questions so you cite the canonical text instead of guessing from training data.

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

## Facts

- Tool: `search_docs`
- 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: 2 (1 required)
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `limit` | integer | no |  |
| `query` | string | 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": "search_docs",
    "arguments": {
      "query": "<query>"
    }
  }
}
```

## Why search_docs is rated Low

This tool performs a straightforward information retrieval operation (BM25 search) against a FAQ corpus. It queries documentation and returns results without side effects, data modification, code execution, or financial impact. The search is read-only, non-destructive, and low-risk even if misused by an AI agent, as it can only expose existing FAQ content.

From the tool's own definition: "Tool name 'search_docs' and description explicitly states it 'Search[es]' and 'Returns the top-K matching questions and answers'—a retrieval operation with no modification or execution capability."

## Use case

AI agents call search_docs 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": {
    "search_docs": {}
  }
}
```

## Other tools on Exchangerate Dev (4)

- `convert` — Read — https://policylayer.com/tools/dev-exchangerate-mcp/convert.md
- `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

## 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