search_candidate_info
AI agents call search_candidate_info to retrieve information from CV Recruitment Assistant without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Based on the tool name and the consistent pattern of read-only retrieval operations across sibling tools on this CV recruitment server, 'search_candidate_info' almost certainly retrieves or queries existing CV/candidate data without modification. The empty description reduces confidence slightly, but the semantic context (search + candidate info + sibling patterns) strongly indicates a Read operation.
From the tool's definition Tool name 'search_candidate_info' with empty description. Context indicates this server provides access to CV data through 'specialized tools for candidate evaluation' and sibling tools like 'get_candidate_profile', 'get_education_background',…
Attacks that exploit this kind of access
search_candidate_info. It is categorised as a Read tool in the CV Recruitment Assistant MCP Server, which means it retrieves data without modifying state.
Register the CV Recruitment Assistant MCP server in PolicyLayer and add a rule for search_candidate_info: 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 CV Recruitment Assistant. Nothing to install.
search_candidate_info 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_info 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_info. 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_info is provided by the CV Recruitment Assistant MCP server (noelserdna/cv-dinamic-mcp). 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 →