get_certifications
AI agents call get_certifications 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 certification information from a candidate's CV data. It performs read-only access to existing candidate information with no side effects, modification, deletion, or external execution capabilities. The 'get_' prefix and alignment with similar sibling tools confirm this is a retrieval operation. Severity is low because accessing publicly-facing CV data carries minimal risk of harm.
From the tool's definition Tool name 'get_certifications' and pattern matching sibling tools (get_candidate_profile, get_education_background, get_github_profile, get_portfolio_website, get_social_networks, get_languages_interests) which are all retrieval operations.
Attacks that exploit this kind of access
get_certifications. 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_certifications: 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_certifications 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_certifications 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_certifications. 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_certifications 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 →