translate_chat_message

Attempt to translate a located Huly channel/DM message to targetLanguage. Current Huly translation is browser-only, uses an optional AI endpoint, and stores results only in UI state; this build returns supported=false with a stable reasonCode and does not fabricate translated text.

SERVERHuly SOURCE@firfi/huly-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-dearlordylord-huly-mcp/translate-chat-message.md

WHAT IT DOES

What translate_chat_message does on Huly

AI agents call translate_chat_message to retrieve information from Huly without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why translate_chat_message is rated Low

This tool retrieves translation information for an existing message without modifying the message itself, changing channel state, or executing arbitrary code. It reads data (the message) and returns a translation result stored transiently in UI state. No data is persisted, deleted, or created in the system.

From the tool's definition Tool description states it 'Attempt to translate a located Huly channel/DM message' and 'stores results only in UI state' with no modification to underlying data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs translate_chat_message safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Huly, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For translate_chat_message, this is the rule to start with:

translate_chat_message Allowed

translate_chat_message is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "translate_chat_message": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Huly, apply this rule, and every translate_chat_message call is checked against it from then on.

FAQ

Questions about translate_chat_message

What does the translate_chat_message tool do? +

How do I enforce a policy on translate_chat_message? +

Register the Huly MCP server in PolicyLayer and add a rule for translate_chat_message: 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 Huly. Nothing to install.

What risk level is translate_chat_message? +

translate_chat_message is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit translate_chat_message? +

Yes. Add a rate_limit block to the translate_chat_message 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.

How do I block translate_chat_message completely? +

Set action: deny in the PolicyLayer policy for translate_chat_message. 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.

What MCP server provides translate_chat_message? +

translate_chat_message is provided by the Huly MCP server (@firfi/huly-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Huly, and thousands of servers like it.

This server

All 518 Huly tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →