list_candidates
AI agents call list_candidates to retrieve information from Bullhorn CRM 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 or lists candidate records from the CRM without modifying data. While the description is empty, the name and context of sibling read-only tools strongly suggest it performs a simple list/fetch operation on candidate entities. The blast radius of misuse is limited to unauthorized data access rather than modification, deletion, or financial impact.
From the tool's definition Tool name 'list_candidates' combined with sibling tools like 'get_candidate', 'get_job', 'list_jobs', and 'query_entities' indicates data retrieval operations. The server enables 'query Bullhorn CRM data' with no mention of modification capabilities.
Attacks that exploit this kind of access
list_candidates. It is categorised as a Read tool in the Bullhorn CRM MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Bullhorn CRM MCP Server MCP server in PolicyLayer and add a rule for list_candidates: 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 Bullhorn CRM MCP Server. Nothing to install.
list_candidates 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 list_candidates 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 list_candidates. 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.
list_candidates is provided by the Bullhorn CRM MCP Server MCP server (osherai/bullhorn-mcp-python). 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 →