AI agents call ai_translate to retrieve information from Run402 without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Text translation is a data retrieval and transformation service. While it requires a service key and active AI Translation add-on (indicating billable usage), the tool itself does not execute commands, modify data structures, delete information, or directly commit financial transactions. The financial component (paid add-on) is infrastructure-level access control, not a direct financial operation by the tool.
From the tool's definition Tool description states 'Translate text to a target language' — a read-only operation that retrieves or transforms input text without modifying, deleting, executing code, or moving money. No side effects mentioned.
Attacks that exploit this kind of access
Translate text to a target language. Requires service key and active AI Translation add-on. Supports optional source language and context hint. It is categorised as a Read tool in the Run402 MCP Server, which means it retrieves data without modifying state.
Register the Run402 MCP server in PolicyLayer and add a rule for ai_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 Run402. Nothing to install.
ai_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 ai_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 ai_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.
ai_translate is provided by the Run402 MCP server (kychee-com/run402). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →