libretranslate_detect
Detect the language of a text using LibreTranslate.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/libretranslate-detect.md
What libretranslate_detect does on UnClick
AI agents call libretranslate_detect 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 |
|---|---|---|---|
text | string | Yes | Text to detect language of. |
Parameters from the server's own tool schema.
Why libretranslate_detect is rated Low
Language detection is a read-only operation that retrieves or infers metadata about the input text (its language) without altering data, executing arbitrary code, or triggering external operations beyond the detection service itself. The blast radius of misuse is minimal—an agent could be misled about language, but this poses no security, financial, or destructive risk.
From the tool's definition Tool name 'libretranslate_detect' and description 'Detect the language of a text using LibreTranslate' indicate a language detection operation that analyzes input text and returns the detected language without modifying, executing code, or creating side…
Attacks that exploit this kind of access
The rule that runs libretranslate_detect 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 libretranslate_detect, this is the rule to start with:
libretranslate_detect 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 libretranslate_detect call is checked against it from then on.
Questions about libretranslate_detect
Detect the language of a text using LibreTranslate. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
libretranslate_detect accepts 1 parameter: text. Required: text. 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 libretranslate_detect: 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.
libretranslate_detect 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 libretranslate_detect 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 libretranslate_detect. 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.
libretranslate_detect 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