spellcheck_vro
AI agents call spellcheck_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.
Spellchecking is fundamentally a read operation that analyzes input text and reports results (errors/suggestions) without side effects. The description is empty, which slightly lowers confidence, but the tool name and context of peer tools strongly indicate it is a non-destructive analysis tool. No modification, execution, deletion, or financial operations are implied. Classified as Read with low severity.
From the tool's definition Tool name 'spellcheck_vro' indicates a spell-checking function for the Võro language. Based on sibling tools (analyze_word, grammar_check_vro, find_unknown_words) that are all analysis/checking utilities, this tool performs static analysis of text to identify…
Attacks that exploit this kind of access
spellcheck_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 spellcheck_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.
spellcheck_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 spellcheck_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 spellcheck_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.
spellcheck_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 →