# translate-document

Translate a document file via DeepL

Agent View of the PolicyLayer registry record for `translate-document`. HTML page: https://policylayer.com/tools/deepl/translate-document

## Facts

- Tool: `translate-document`
- Server: DeepL (`@deepl-mcp-server`) — https://policylayer.com/tools/deepl.md
- Install: `npx -y @deepl-mcp-server`
- Homepage: https://www.npmjs.com/package/@deepl-mcp-server
- Risk category: Execute (High risk)
- Registry record: grade C, identity verified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Rate-limited

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

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "translate-document",
    "arguments": {}
  }
}
```

## Why translate-document is rated High

This tool executes a document translation operation, which is an external service call with effects dependent on the input document and target language parameters. While the operation is reversible (not Destructive) and does not move money (not Financial), it performs a transformation on user data via an external API.

From the tool's own definition: "Tool description: 'Translate a document file via DeepL' — the tool processes and translates document files, which constitutes execution of a translation operation on user-provided input."

Risk signals: Sends documents to external DeepL API

## Use case

AI agents invoke translate-document to trigger actions in DeepL. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches DeepL:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "translate-document": {
      "limits": [
        {
          "counter": "translate-document_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on DeepL (8)

- `get-glossary-dictionary-entries` — Read — https://policylayer.com/tools/deepl/get-glossary-dictionary-entries.md
- `get-glossary-info` — Read — https://policylayer.com/tools/deepl/get-glossary-info.md
- `get-source-languages` — Read — https://policylayer.com/tools/deepl/get-source-languages.md
- `get-target-languages` — Read — https://policylayer.com/tools/deepl/get-target-languages.md
- `get-writing-styles` — Read — https://policylayer.com/tools/deepl/get-writing-styles.md
- `list-glossaries` — Read — https://policylayer.com/tools/deepl/list-glossaries.md
- `translate-text` — Read — https://policylayer.com/tools/deepl/translate-text.md
- `rephrase-text` — Write — https://policylayer.com/tools/deepl/rephrase-text.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=deepl · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/deepl