Get the total count of candidates matching specific criteria without returning all the data. Perfect for answering
AI agents call get_candidate_count 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 performs a read-only query operation that returns a count statistic. It has no side effects, does not modify data, and poses minimal risk even if misused—an agent retrieving incorrect candidate counts would not cause harm to the system or data integrity.
From the tool's definition Tool name 'get_candidate_count' and description indicate it retrieves aggregated count data ('Get the total count of candidates matching specific criteria without returning all the data').
Attacks that exploit this kind of access
Get the total count of candidates matching specific criteria without returning all the data. Perfect for answering. 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 get_candidate_count: 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.
get_candidate_count 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 get_candidate_count 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 get_candidate_count. 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.
get_candidate_count 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.
get_candidate_count is one line of Viterbit MCP Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →