evaluate_tech_stack
AI agents call evaluate_tech_stack 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.
The tool appears to retrieve or analyze technical skill data from the candidate's CV/profile for evaluation purposes, consistent with the server's stated function of candidate assessment. No indication of data modification, execution of external code, deletion, or financial operations.
From the tool's definition Tool name 'evaluate_tech_stack' suggests assessment/evaluation of technical skills; server context shows this is a 'Recruitment Assistant' for 'candidate evaluation' with sibling tools like 'assess_leadership_experience', 'get_certifications',…
Attacks that exploit this kind of access
evaluate_tech_stack. 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 evaluate_tech_stack: 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.
evaluate_tech_stack 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 evaluate_tech_stack 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 evaluate_tech_stack. 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.
evaluate_tech_stack 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 →