get_candidates_from_pipeline_for_evaluation
AI agents call get_candidates_from_pipeline_for_evaluation to retrieve information from Recruitee MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves candidate information for evaluation purposes. The empty description and '_for_evaluation' context suggest it queries and returns candidate data from the pipeline without creating, modifying, deleting, or executing operations. It is consistent with other Read tools on the server (get_candidate_profile, get_candidate_notes).
From the tool's definition Tool name 'get_candidates_from_pipeline' and server description indicate data retrieval from Recruitee recruitment pipelines. Sibling tools like 'get_candidate_profile' and 'search_candidates' confirm a Read-only pattern.
Attacks that exploit this kind of access
get_candidates_from_pipeline_for_evaluation. It is categorised as a Read tool in the Recruitee MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Recruitee MCP Server MCP server in PolicyLayer and add a rule for get_candidates_from_pipeline_for_evaluation: 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 Recruitee MCP Server. Nothing to install.
get_candidates_from_pipeline_for_evaluation 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_candidates_from_pipeline_for_evaluation 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_candidates_from_pipeline_for_evaluation. 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_candidates_from_pipeline_for_evaluation is provided by the Recruitee MCP Server MCP server (pepuscz/recruitee-mcp-server). 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 →