get-target-languages

Get list of available target languages

SERVERDeepL SOURCE@deepl-mcp-server

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade C, identity verified Pull the record →

This record as markdown: /tools/deepl/get-target-languages.md

WHAT IT DOES

What get-target-languages does on DeepL

AI agents call get-target-languages to retrieve information from DeepL without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why get-target-languages is rated Low

This tool retrieves a static list of supported languages from the DeepL API. It performs no data modification, deletion, or external operations—only a simple informational query. The blast radius of misuse is minimal; returning an incorrect language list would not compromise data integrity or enable unauthorized actions.

From the tool's definition Tool name 'get-target-languages' and description 'Get list of available target languages' indicate a query/retrieval operation that returns data without modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get-target-languages 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 get-target-languages, this is the rule to start with:

get-target-languages Allowed

get-target-languages is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get-target-languages": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect DeepL, apply this rule, and every get-target-languages call is checked against it from then on.

FAQ

Questions about get-target-languages

What does the get-target-languages tool do? +

Get list of available target languages. It is categorised as a Read tool in the DeepL MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get-target-languages? +

Register the DeepL MCP server in PolicyLayer and add a rule for get-target-languages: 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.

What risk level is get-target-languages? +

get-target-languages is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get-target-languages? +

Yes. Add a rate_limit block to the get-target-languages 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.

How do I block get-target-languages completely? +

Set action: deny in the PolicyLayer policy for get-target-languages. 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 get-target-languages? +

get-target-languages 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.

KEEP EXPLORING

More on DeepL, and thousands of servers like it.

This server

All 9 DeepL tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →