Get full candidate details including custom fields and address information. Requires candidate ID.
AI agents call get_candidate_details 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 candidate information by ID without modifying, deleting, or executing any operations. It has no side effects beyond reading existing data. The blast radius of misuse is limited to unauthorized information access, making it low severity in a recruitment context where candidate details, while potentially sensitive, are primarily informational.
From the tool's definition Tool name 'get_candidate_details' and description 'Get full candidate details' explicitly indicate data retrieval. The verb 'Get' and the absence of any modification, deletion, or execution language confirm this is a query operation.
Attacks that exploit this kind of access
Get full candidate details including custom fields and address information. Requires candidate ID. 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_details: 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_details 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_details 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_details. 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_details 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 →