Count how many candidatures are currently in a specific stage right now. Returns just the count number for quick reporting about current stage status.
AI agents call count_candidatures_in_current_stage 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 purely retrieves aggregated data (a count) about candidatures in a specific stage. It performs a query operation with no side effects, no data modification, and no irreversible actions. The blast radius of misuse is minimal—an AI agent could only obtain accurate or inaccurate counts of recruitment pipeline metrics, which presents negligible security risk.
From the tool's definition Tool name and description indicate counting/querying: 'Count how many candidatures are currently in a specific stage' and 'Returns just the count number for quick reporting about current stage status.' No modification, deletion, or execution of external…
Attacks that exploit this kind of access
Count how many candidatures are currently in a specific stage right now. Returns just the count number for quick reporting about current stage status. 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 count_candidatures_in_current_stage: 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.
count_candidatures_in_current_stage 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 count_candidatures_in_current_stage 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 count_candidatures_in_current_stage. 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.
count_candidatures_in_current_stage 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 →