Fetch full posting text for job urls from search_jobs. Set search_mode resume_match when fetching postings to compare against the user's resume or background; keyword_search otherwise. Greenhouse (including embedded careers pages), Ashby, and Lever are supported; other career sites may return uns...
AI agents call get_job_details to retrieve information from OpenJob without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
url | string | — | Single job url from search_jobs results. |
urls | array | — | Up to 10 job urls — preferred after resume match. |
search_mode | string | — | keyword_search = role/location/filters only; resume_match = user uploaded a resume (CV) or asked to match jobs to their background or ChatGPT memory. |
user_intent | string | — | A concise summary of what the user is trying to accomplish, derived from their message or the conversation context that triggered this tool call. This is used t |
Parameters from the server's own tool schema.
This tool executes a read-only query against job posting databases, returning posting text and metadata for comparison purposes. The operation has no side effects on the underlying data—it neither creates, modifies, deletes, nor executes code or external operations. The most severe action is filtering/comparing resume data against postings, which remains a retrieval operation.
From the tool's definition Tool retrieves full posting text for job URLs from search results; performs read-only fetch operations without modifying, creating, or deleting data.
Risk signalsAccepts URL/endpoint input (url)
Attacks that exploit this kind of access
Fetch full posting text for job urls from search_jobs. Set search_mode resume_match when fetching postings to compare against the user's resume or background; keyword_search otherwise. Greenhouse (including embedded careers pages), Ashby, and Lever are supported; other career sites may return unsupported_ats. Closed roles are cached about 24 hours; open postings about 14 days (posting text only, not user resumes). Use description_text to compare against the user's resume or stated background. It is categorised as a Read tool in the OpenJob MCP Server, which means it retrieves data without modifying state.
get_job_details accepts 4 parameters: url, urls, search_mode, user_intent. The full parameter table on this page comes from the server's own tool schema.
Register the OpenJob MCP server in PolicyLayer and add a rule for get_job_details: 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 OpenJob. Nothing to install.
get_job_details 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_details 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_details. 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_details is provided by the OpenJob MCP server (https://openjobs-3168f222.alpic.live). 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 →