lookup_word
AI agents call lookup_word 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 retrieves linguistic data from a local dictionary or corpus without modifying, executing code, or triggering external side effects. Lookup operations are inherently read-only and pose minimal security risk. The low confidence penalty is applied only because the description is empty, but the tool name and server context provide strong inference.
From the tool's definition Tool name 'lookup_word' indicates a dictionary/corpus lookup operation. Server description explicitly mentions 'local dictionary and corpus lookup' as a core function.
Attacks that exploit this kind of access
lookup_word. 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 lookup_word: 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.
lookup_word 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 lookup_word 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 lookup_word. 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.
lookup_word 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 →