translate.text.translate
Translate text between 90+ languages — auto-detects source language, supports batch translation (array of strings), HTML format preservation. Google Translate v2 compatible. $5/1M chars (Langbly)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/translate.text.translate.md
What translate.text.translate does on Apibase
AI agents call translate.text.translate to retrieve information from Apibase 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 | object | Yes | Text to translate — single string or array of strings for batch translation |
format | string | — | Input format: "text" (default) or "html" (preserves HTML tags) |
source | string | — | Source language code (auto-detected if omitted) |
target | string | Yes | Target language code (e.g. "es", "fr", "de", "ja", "zh", "ru", "ar") |
Parameters from the server's own tool schema.
Why translate.text.translate is rated Low
Tool translates text without modifying, deleting, or executing code. Pure data transformation with no side effects.
From the tool's definition Translate text between 90+ languages, auto-detects source language, supports batch translation
Attacks that exploit this kind of access
The rule that runs translate.text.translate safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For translate.text.translate, this is the rule to start with:
translate.text.translate 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 Apibase, apply this rule, and every translate.text.translate call is checked against it from then on.
Questions about translate.text.translate
Translate text between 90+ languages — auto-detects source language, supports batch translation (array of strings), HTML format preservation. Google Translate v2 compatible. $5/1M chars (Langbly). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
translate.text.translate accepts 4 parameters: text, format, source, target. Required: text, target. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for translate.text.translate: 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 Apibase. Nothing to install.
translate.text.translate 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.translate 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.translate. 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.translate is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue