deepl_translate_document
Submit a document (PDF, Word, PowerPoint) for translation via DeepL.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/deepl-translate-document.md
What deepl_translate_document does on UnClick
AI agents call deepl_translate_document to retrieve information from UnClick 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 |
|---|---|---|---|
auth_key | string | Yes | DeepL Auth Key |
filename | string | — | Filename with extension (e.g. report.pdf) |
formality | string | — | Formality level |
source_lang | string | — | Source language code (auto-detected if omitted) |
target_lang | string | Yes | Target language code (e.g. DE, FR, JA) |
document_url | string | Yes | Publicly accessible URL of the document to translate |
Parameters from the server's own tool schema.
Why deepl_translate_document is rated Low
Even though deepl_translate_document only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Risk signalsAccepts file system path (filename)
Attacks that exploit this kind of access
The rule that runs deepl_translate_document 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 deepl_translate_document, this is the rule to start with:
deepl_translate_document 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 UnClick, apply this rule, and every deepl_translate_document call is checked against it from then on.
Questions about deepl_translate_document
Submit a document (PDF, Word, PowerPoint) for translation via DeepL. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
deepl_translate_document accepts 6 parameters: auth_key, filename, formality, source_lang, target_lang, document_url. Required: auth_key, target_lang, document_url. 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 deepl_translate_document: 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.
deepl_translate_document 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 deepl_translate_document 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 deepl_translate_document. 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.
deepl_translate_document 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