Check if a candidate should be included in reports based on their activity status and other filtering criteria.
AI agents call check_candidate_eligibility to retrieve information from Viterbit 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 or evaluates candidate information against eligibility criteria to inform reporting decisions. It has no side effects—it does not create, modify, delete, or execute external operations. It is purely informational/read-only, consistent with similar tools on the server (get_candidate_details, get_candidate_with_filters).
From the tool's definition Tool name 'check_candidate_eligibility' and description indicate it 'check[s] if a candidate should be included' based on filtering criteria.
Attacks that exploit this kind of access
Check if a candidate should be included in reports based on their activity status and other filtering criteria. It is categorised as a Read tool in the Viterbit MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Viterbit MCP Server MCP server in PolicyLayer and add a rule for check_candidate_eligibility: 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 Viterbit MCP Server. Nothing to install.
check_candidate_eligibility 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_candidate_eligibility 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_candidate_eligibility. 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_candidate_eligibility is provided by the Viterbit MCP Server MCP server (techkampe/mcp_viterbit). 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 →