mymemory_translate
Translate text between languages using MyMemory free translation API.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/mymemory-translate.md
What mymemory_translate does on UnClick
AI agents call mymemory_translate 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 translate. |
source | string | — | Source language code (default: en). |
target | string | — | Target language code (default: es). |
Parameters from the server's own tool schema.
Why mymemory_translate is rated Low
The tool performs a straightforward translation lookup—a read-only operation that queries an external API and returns translated text. No side effects, no data modification, no code execution, no destructive actions, and no financial implications. This falls squarely into the Read category.
From the tool's definition Tool description states it 'Translate[s] text between languages using MyMemory free translation API.' This is a query operation that retrieves translation data without modifying, executing code, deleting data, or moving money.
Attacks that exploit this kind of access
The rule that runs mymemory_translate 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 mymemory_translate, this is the rule to start with:
mymemory_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 UnClick, apply this rule, and every mymemory_translate call is checked against it from then on.
Questions about mymemory_translate
Translate text between languages using MyMemory free translation API. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
mymemory_translate accepts 3 parameters: text, source, target. 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 mymemory_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 UnClick. Nothing to install.
mymemory_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 mymemory_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 mymemory_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.
mymemory_translate 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