translate_text
Translate text between languages using Nextcloud's configured translation provider. If called without text, returns available language pairs.
This record as markdown: /tools/aiquila-nextcloud-mcp-server/translate-text.md
What translate_text does on AIquila — Nextcloud MCP Server
AI agents call translate_text to retrieve information from AIquila — Nextcloud MCP Server 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 | — | Text to translate. Omit to list available language pairs. |
toLanguage | string | — | Target language code (e.g. 'en', 'de', 'fr') |
fromLanguage | string | — | Source language code (e.g. 'en', 'de', 'fr') |
Parameters from the server's own tool schema.
Why translate_text is rated Low
Translation is a stateless transformation service that reads input text and returns translated output. It does not create, modify, delete, or execute any external operations. It does not commit to financial obligations or irreversibly change any data. The tool either translates provided text (read + transform) or returns available language pair metadata (read). This is purely a Read operation.
From the tool's definition Tool description states 'Translate text between languages using Nextcloud's configured translation provider.
Attacks that exploit this kind of access
The rule that runs translate_text safely
PolicyLayer is an MCP gateway: it sits between your AI agents and AIquila — Nextcloud MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For translate_text, this is the rule to start with:
translate_text 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 AIquila — Nextcloud MCP Server, apply this rule, and every translate_text call is checked against it from then on.
Questions about translate_text
Translate text between languages using Nextcloud's configured translation provider. If called without text, returns available language pairs. It is categorised as a Read tool in the AIquila — Nextcloud MCP Server MCP Server, which means it retrieves data without modifying state.
translate_text accepts 3 parameters: text, toLanguage, fromLanguage. The full parameter table on this page comes from the server's own tool schema.
Register the AIquila — Nextcloud MCP Server MCP server in PolicyLayer and add a rule for translate_text: 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 AIquila — Nextcloud MCP Server. Nothing to install.
translate_text 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 translate_text 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_text. 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_text is provided by the AIquila — Nextcloud MCP Server MCP server (elgorro/aiquila). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on AIquila — Nextcloud MCP Server, and thousands of servers like it.
This server
Across the catalogue