get_candidate_profile
AI agents call get_candidate_profile 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.
This tool retrieves candidate profile information as part of a CV/recruitment evaluation system. No side effects, modifications, deletions, code execution, or financial operations are implied. The absence of a description is mitigated by strong contextual evidence from sibling tools and naming convention, all indicating read-only data access for candidate evaluation purposes.
From the tool's definition Tool name 'get_candidate_profile' with sibling tools like 'get_certifications', 'get_education_background', 'get_github_profile', 'get_social_networks', and 'get_portfolio_website' indicates retrieval of existing candidate data.
Attacks that exploit this kind of access
get_candidate_profile. 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 get_candidate_profile: 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.
get_candidate_profile 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_profile 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_profile. 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_profile 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 →