AI agents call listLanguages to retrieve information from Translate without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries data about available languages without modifying, executing external operations, or causing any irreversible changes. It is a straightforward read operation with minimal security risk.
From the tool's definition Tool name 'listLanguages' and description '列出支持的语言' (list supported languages) indicate a query operation that retrieves a static list of supported languages with no side effects.
Attacks that exploit this kind of access
列出支持的语言. It is categorised as a Read tool in the Translate MCP Server, which means it retrieves data without modifying state.
Register the Translate MCP server in PolicyLayer and add a rule for listLanguages: 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 Translate. Nothing to install.
listLanguages 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 listLanguages 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 listLanguages. 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.
listLanguages is provided by the Translate MCP server (translate-mcp-server). 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 →