High Risk →

translate-document

Translate a document file via DeepL

Sends documents to external DeepL API

Part of the DeepL MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

@deepl-mcp-server Execute Risk 3/5

AI agents invoke translate-document to trigger processes or run actions in DeepL. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.

translate-document can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.

Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.

deepl.yaml
tools:
  translate-document:
    rules:
      - action: allow
        rate_limit:
          max: 10
          window: 60
        validate:
          required_args: true

See the full DeepL policy for all 9 tools.

Tool Name translate-document
Category Execute
MCP Server DeepL MCP Server
Risk Level High

View all 9 tools →

Agents calling execute-class tools like translate-document have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

translate-document is one of the high-risk operations in DeepL. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.

What does the translate-document tool do? +

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.

How do I enforce a policy on translate-document? +

Add a rule in your Intercept YAML policy under the tools section for translate-document. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the DeepL MCP server.

What risk level is translate-document? +

translate-document is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit translate-document? +

Yes. Add a rate_limit block to the translate-document rule in your Intercept 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.

How do I block translate-document completely? +

Set action: deny in the Intercept 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.

What MCP server provides translate-document? +

translate-document is provided by the DeepL MCP server (@deepl-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on DeepL

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.