word_exists_in_bag
AI agents call word_exists_in_bag 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 check whether a word exists in a lexical resource (a 'bag' likely refers to a word bag or dictionary). The operation is read-only—it queries data without modifying, creating, executing code, or deleting anything. The empty description lowers confidence slightly, but the naming convention and context of sibling tools strongly indicate a simple lookup operation with no side effects.
From the tool's definition Tool name is 'word_exists_in_bag' suggesting a simple lookup operation against a dictionary or corpus. Sibling tools include 'analyze_word', 'find_usage_examples', and other read-only language analysis operations, confirming the pattern of retrieval-based…
Attacks that exploit this kind of access
word_exists_in_bag. 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 word_exists_in_bag: 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.
word_exists_in_bag 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 word_exists_in_bag 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 word_exists_in_bag. 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.
word_exists_in_bag 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 →