Count how many candidatures changed to a specific stage during a given month. Returns just the count number for quick reporting.
AI agents call count_candidatures_changed_to_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 retrieves aggregated statistics about candidatures without creating, modifying, deleting, or executing any operations. It is a simple counting/reporting function that queries historical data for analytics purposes. Minimal blast radius if misused—worst case would be information disclosure of recruitment metrics.
From the tool's definition Tool description states it 'Count[s] how many candidatures changed to a specific stage' and 'Returns just the count number for quick reporting.' This is a query/retrieval operation with no modification of data.
Attacks that exploit this kind of access
Count how many candidatures changed to a specific stage during a given month. Returns just the count number for quick reporting. 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_changed_to_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_changed_to_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_changed_to_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_changed_to_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_changed_to_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 →