jobs.occupations.details
Get detailed occupation info from O*NET by SOC code — overview, skills, knowledge, abilities, technology skills, tasks
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/jobs.occupations.details.md
What jobs.occupations.details does on Apibase
AI agents call jobs.occupations.details to retrieve information from Apibase without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
code | string | Yes | O*NET SOC occupation code (e.g. "15-1252.00" for Software Developers). Get codes from occupation_search. |
section | string | — | Specific section to retrieve. Omit for general overview (title, description, sample titles). |
Parameters from the server's own tool schema.
Why jobs.occupations.details is rated Low
Tool retrieves occupation reference data without modification, deletion, or execution capabilities.
From the tool's definition Get detailed occupation info from O*NET by SOC code
Risk signalsAccepts freeform code/query input (code)
Attacks that exploit this kind of access
The rule that runs jobs.occupations.details safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For jobs.occupations.details, this is the rule to start with:
jobs.occupations.details is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Apibase, apply this rule, and every jobs.occupations.details call is checked against it from then on.
Questions about jobs.occupations.details
Get detailed occupation info from O*NET by SOC code — overview, skills, knowledge, abilities, technology skills, tasks. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
jobs.occupations.details accepts 2 parameters: code, section. Required: code. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for jobs.occupations.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 Apibase. Nothing to install.
jobs.occupations.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 jobs.occupations.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 jobs.occupations.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.
jobs.occupations.details is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue