jobs.skills.search
Search ESCO (European Skills/Competences/Occupations) taxonomy — occupations and skills in 27 EU languages
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/jobs.skills.search.md
What jobs.skills.search does on Apibase
AI agents call jobs.skills.search 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 |
|---|---|---|---|
text | string | Yes | Search text for EU occupations or skills (e.g. "software developer", "project management"). |
type | string | — | Resource type to search. Default: "occupation". |
limit | integer | — | Results per page (default 25, max 100). |
offset | integer | — | Offset for pagination. Omit for first page. |
language | string | — | ISO 639-1 language code (e.g. "en", "de", "fr"). Default: "en". ESCO supports 27 EU languages. |
Parameters from the server's own tool schema.
Why jobs.skills.search is rated Low
Tool queries a skills taxonomy database without modifying data or executing external operations.
From the tool's definition Search ESCO taxonomy — occupations and skills
Attacks that exploit this kind of access
The rule that runs jobs.skills.search 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.skills.search, this is the rule to start with:
jobs.skills.search 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.skills.search call is checked against it from then on.
Questions about jobs.skills.search
Search ESCO (European Skills/Competences/Occupations) taxonomy — occupations and skills in 27 EU languages. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
jobs.skills.search accepts 5 parameters: text, type, limit, offset, language. Required: text. 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.skills.search: 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.skills.search 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.skills.search 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.skills.search. 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.skills.search 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