find_estonian_leakage
AI agents call find_estonian_leakage 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.
This tool appears to scan or analyze text to identify Estonian language influence in Võro text (detecting 'leakage'). This is a read-only analysis operation that retrieves or identifies patterns without modifying data or triggering external effects. No side effects, deletions, or financial impact. Low severity due to its informational nature and limited blast radius if misused by an AI agent.
From the tool's definition Tool name 'find_estonian_leakage' combined with sibling tools like 'lint_estonian_leakage' and 'find_unknown_words' suggests text analysis/scanning. The server description indicates these are language analysis tools backed by GiellaLT.
Attacks that exploit this kind of access
find_estonian_leakage. 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 find_estonian_leakage: 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.
find_estonian_leakage 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 find_estonian_leakage 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 find_estonian_leakage. 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.
find_estonian_leakage 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 →