Search for a candidate by name, email address, or phone number. Returns basic candidate information including ID, name, email, and phone.
AI agents call search_candidate 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.
search_candidate performs a lookup operation that retrieves existing candidate data without creating, modifying, deleting, or executing any operations. This is a classic Read category tool. Severity is low because exposure of candidate search capability poses minimal risk — it returns basic informational data that recruitment systems typically allow authorized users to query.
From the tool's definition Tool description states it 'Search for a candidate' and 'Returns basic candidate information' — a query operation with no modification or side effects. The action is retrieval-only.
Attacks that exploit this kind of access
Search for a candidate by name, email address, or phone number. Returns basic candidate information including ID, name, email, and phone. 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 search_candidate: 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.
search_candidate 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 search_candidate 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 search_candidate. 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.
search_candidate 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 →