Get details for a specific job order by ID.
AI agents call get_job 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 job order information from Bullhorn CRM without modifying, deleting, or executing any operations. It is a straightforward query operation that returns existing data. The severity is low because exposure of this tool to an AI agent presents minimal risk—the worst outcome is unauthorized disclosure of job data, which is a confidentiality concern but not operationally damaging or irreversible.
From the tool's definition Tool name 'get_job' and description 'Get details for a specific job order by ID' indicate data retrieval only. The verb 'Get' and the read-only nature of fetching details by ID confirm no side effects.
Attacks that exploit this kind of access
Get details for a specific job order by ID. 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 get_job: 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.
get_job 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_job 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_job. 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_job 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 →