jobs.adzuna.salary
Get salary distribution for a job title — returns histogram of salary buckets with job counts. Example: "python developer" in US → $20K-$140K distribution. Use for salary benchmarking and market research (Adzuna)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/jobs.adzuna.salary.md
What jobs.adzuna.salary does on Apibase
AI agents call jobs.adzuna.salary 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 |
|---|---|---|---|
what | string | — | Job title or keywords for salary histogram (e.g. "python developer", "data scientist") |
where | string | — | Location for salary data |
country | string | — | Country code (default us) |
Parameters from the server's own tool schema.
Why jobs.adzuna.salary is rated Low
Retrieves publicly available salary data with no side effects or external state changes.
From the tool's definition Get salary distribution, returns histogram, salary benchmarking, market research
Attacks that exploit this kind of access
The rule that runs jobs.adzuna.salary 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.adzuna.salary, this is the rule to start with:
jobs.adzuna.salary 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.adzuna.salary call is checked against it from then on.
Questions about jobs.adzuna.salary
Get salary distribution for a job title — returns histogram of salary buckets with job counts. Example: "python developer" in US → $20K-$140K distribution. Use for salary benchmarking and market research (Adzuna). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
jobs.adzuna.salary accepts 3 parameters: what, where, country. 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.adzuna.salary: 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.adzuna.salary 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.adzuna.salary 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.adzuna.salary. 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.adzuna.salary 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