lint_estonian_leakage
AI agents call lint_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 identify instances where Estonian language has leaked into Võro text, similar to linting. No description is provided, but the naming pattern and context strongly suggest it reads and analyzes text to report findings without modifying data or executing arbitrary operations.
From the tool's definition Tool name 'lint_estonian_leakage' and sibling tool 'find_estonian_leakage' indicate detection/analysis rather than modification. The 'lint' prefix typically denotes code/text analysis without side effects.
Attacks that exploit this kind of access
lint_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 lint_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.
lint_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 lint_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 lint_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.
lint_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 →