datasets_jobs_companies
Find which companies are hiring. Searches the discovered company board registry — which companies are hiring, on which ATS, with how many open roles. status enum: active, empty, gone, blocked, pending. sort enum: open_desc, company_asc, crawled_desc.
This record as markdown: /tools/crawlora-mcp/datasets-jobs-companies.md
What datasets_jobs_companies does on Crawlora
AI agents call datasets_jobs_companies to retrieve information from Crawlora 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 |
|---|---|---|---|
q | string | — | Match on company name / domain |
page | integer | — | Page number, default 1 |
sort | string | — | Sort enum: open_desc, company_asc, crawled_desc |
status | string | — | Board status. Enum: active, empty, gone, blocked, pending |
provider | string | — | ATS provider filter |
page_size | integer | — | Page size, default 20, max 100 |
min_open_roles | integer | — | Minimum open roles |
Parameters from the server's own tool schema.
Why datasets_jobs_companies is rated Low
Even though datasets_jobs_companies only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs datasets_jobs_companies safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Crawlora, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For datasets_jobs_companies, this is the rule to start with:
datasets_jobs_companies 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 Crawlora, apply this rule, and every datasets_jobs_companies call is checked against it from then on.
Questions about datasets_jobs_companies
Find which companies are hiring. Searches the discovered company board registry — which companies are hiring, on which ATS, with how many open roles. status enum: active, empty, gone, blocked, pending. sort enum: open_desc, company_asc, crawled_desc. It is categorised as a Read tool in the Crawlora MCP Server, which means it retrieves data without modifying state.
datasets_jobs_companies accepts 7 parameters: q, page, sort, status, provider, page_size, min_open_roles. The full parameter table on this page comes from the server's own tool schema.
Register the Crawlora MCP server in PolicyLayer and add a rule for datasets_jobs_companies: 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 Crawlora. Nothing to install.
datasets_jobs_companies 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 datasets_jobs_companies 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 datasets_jobs_companies. 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.
datasets_jobs_companies is provided by the Crawlora MCP server (crawlora-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Crawlora, and thousands of servers like it.
This server
Across the catalogue