Get all candidatures currently in a specific stage right now. Returns detailed candidature information for candidates in the specified stage at this moment.
AI agents call get_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 is a straightforward query operation that retrieves recruitment candidature data filtered by stage. It has no side effects, does not modify data, and does not execute code or trigger external actions. The blast radius of misuse is limited to unauthorized data disclosure (low severity), as an agent could only read candidate information that should be protected, but cannot change or delete records.
From the tool's definition Tool name contains 'get_' and description states 'Get all candidatures currently in a specific stage' with 'Returns detailed candidature information' — pure data retrieval with no modification, deletion, or execution of external operations.
Attacks that exploit this kind of access
Get all candidatures currently in a specific stage right now. Returns detailed candidature information for candidates in the specified stage at this moment. 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_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.
get_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 get_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 get_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.
get_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 →