deepl_list_languages
List all languages supported by DeepL for translation.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/deepl-list-languages.md
What deepl_list_languages does on UnClick
AI agents call deepl_list_languages 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 |
|---|---|---|---|
type | string | — | Language direction (default: target) |
auth_key | string | Yes | DeepL Auth Key |
Parameters from the server's own tool schema.
Why deepl_list_languages is rated Low
This tool performs a simple informational query to enumerate available languages supported by a translation service. It retrieves data without creating, modifying, deleting, or executing any operations. There is no capability to make API calls that would alter state, trigger external actions, or affect data integrity.
From the tool's definition Tool name and description indicate a list operation that retrieves supported languages from DeepL's API. The verb 'list' and action 'List all languages' are explicit indicators of a read-only query with no side effects.
Attacks that exploit this kind of access
The rule that runs deepl_list_languages 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_list_languages, this is the rule to start with:
deepl_list_languages 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_list_languages call is checked against it from then on.
Questions about deepl_list_languages
List all languages supported by DeepL for translation. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
deepl_list_languages accepts 2 parameters: type, auth_key. Required: auth_key. 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_list_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 UnClick. Nothing to install.
deepl_list_languages 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_list_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.
Set action: deny in the PolicyLayer policy for deepl_list_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.
deepl_list_languages 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