jobs.salary.data
Get US salary and employment timeseries data from BLS — wage estimates, employment counts, occupational statistics by SOC code and geography
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/jobs.salary.data.md
What jobs.salary.data does on Apibase
AI agents call jobs.salary.data 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 |
|---|---|---|---|
end_year | string | — | End year (e.g. "2024"). Omit for latest available. |
series_ids | array | Yes | BLS timeseries IDs (e.g. ["OEUM0000000000000151252004"] for Software Developers mean salary). Encodes occupation code + geography + data type. |
start_year | string | — | Start year (e.g. "2020"). Omit for latest available. |
Parameters from the server's own tool schema.
Why jobs.salary.data is rated Low
Retrieves historical wage and employment statistics; read-only query with no side effects or data modification.
From the tool's definition Get US salary and employment timeseries data from BLS
Attacks that exploit this kind of access
The rule that runs jobs.salary.data 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.salary.data, this is the rule to start with:
jobs.salary.data 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.salary.data call is checked against it from then on.
Questions about jobs.salary.data
Get US salary and employment timeseries data from BLS — wage estimates, employment counts, occupational statistics by SOC code and geography. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
jobs.salary.data accepts 3 parameters: end_year, series_ids, start_year. Required: series_ids. 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.salary.data: 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.salary.data 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.salary.data 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.salary.data. 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.salary.data 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