Report compact database and Giella availability. Healthy components are
AI agents call check_setup 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 is a diagnostic/reporting tool that queries the status of local resources (database and Giella availability). It performs only information retrieval without side effects, making it a Read category tool. Severity is low because misuse cannot harm data integrity, financial systems, or external services—it merely returns status information. High confidence due to clear diagnostic nature of the tool.
From the tool's definition Tool name 'check_setup' and description 'Report compact database and Giella availability' indicate a status/diagnostic query that retrieves information about component health with no modification of data or execution of external operations.
Attacks that exploit this kind of access
Report compact database and Giella availability. Healthy components are. 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 check_setup: 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.
check_setup 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 check_setup 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 check_setup. 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.
check_setup 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 →