translate_vro
AI agents call translate_vro to retrieve information from Võro MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Translation tools retrieve information (translated text) without creating, modifying, deleting, or executing arbitrary code. The empty description reduces confidence slightly, but the server's stated purpose ('translation') and sibling tools (all analysis/lookup operations) support Read classification. No side effects or state changes are typical of translation queries.
From the tool's definition Tool named 'translate_vro' on a language tools server alongside analysis, spellcheck, and lookup utilities. The description is empty, but context indicates this is a translation tool (Neurotõlge mentioned in server description).
Attacks that exploit this kind of access
translate_vro. It is categorised as a Read tool in the Võro MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Võro MCP Server MCP server in PolicyLayer and add a rule for translate_vro: 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 Võro MCP Server. Nothing to install.
translate_vro 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_vro 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_vro. 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_vro is provided by the Võro MCP Server MCP server (leo-martin-pala/voro-mcp). 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 →