This record as markdown: /tools/deepl/translate-document.md
What translate-document does on DeepL
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.
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 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 signalsSends documents to external DeepL API
Attacks that exploit this kind of access
The rule that runs translate-document safely
PolicyLayer is an MCP gateway: it sits between your AI agents and DeepL, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For translate-document, this is the rule to start with:
translate-document stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect DeepL, apply this rule, and every translate-document call is checked against it from then on.
Questions about translate-document
Translate a document file via DeepL. It is categorised as a Execute tool in the DeepL MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the DeepL MCP server in PolicyLayer and add a rule for 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 DeepL. Nothing to install.
translate-document is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the 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 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.
translate-document is provided by the DeepL MCP server (@deepl-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on DeepL, and thousands of servers like it.
This server
Across the catalogue