Get candidature details including complete stages history. Shows all stage transitions with timestamps.
AI agents call get_candidature_stage_history 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 and displays candidature stage transition history with timestamps. It queries existing data without creating, modifying, deleting, or executing any operations. The blast radius of misuse is minimal—an attacker could view recruitment pipeline history but cannot alter applications, candidate data, or trigger external actions. This is a straightforward data retrieval operation.
From the tool's definition Tool name 'get_candidature_stage_history' and description 'Get candidature details including complete stages history' indicates retrieval of historical data with no modification. The verb 'Get' and 'Shows' confirm read-only operations.
Attacks that exploit this kind of access
Get candidature details including complete stages history. Shows all stage transitions with timestamps. 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_candidature_stage_history: 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_candidature_stage_history 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_candidature_stage_history 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_candidature_stage_history. 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_candidature_stage_history 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 →