jobs_workday_board
List a Workday tenant's job board. Lists a company's public Workday (CXS) postings, paged via limit/offset. tenant, datacenter (wd1/wd3/wd5/...), and site all come from the careers URL https://{tenant}.wd5.myworkdayjobs.com/{site}. Credential-free public ATS JSON.
This record as markdown: /tools/crawlora-mcp/jobs-workday-board.md
What jobs_workday_board does on Crawlora
AI agents call jobs_workday_board 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 |
|---|---|---|---|
site | string | Yes | Workday career site |
limit | integer | — | Page size, default 20, max 20 |
offset | integer | — | Page offset, default 0 |
search | string | — | Free-text search |
tenant | string | Yes | Workday tenant |
datacenter | string | Yes | Workday datacenter shard (wd1, wd3, wd5, ...) |
Parameters from the server's own tool schema.
Why jobs_workday_board is rated Low
This tool retrieves publicly available job posting data from Workday's ATS system. There are no side effects—it does not create, modify, delete, or execute operations. The data is explicitly public and credential-free, making it a straightforward Read operation with minimal risk. The blast radius is low since it only accesses non-sensitive, already-public information.
From the tool's definition Tool description states it 'Lists a company's public Workday (CXS) postings' and retrieves 'public ATS JSON' without authentication ('Credential-free').
Attacks that exploit this kind of access
The rule that runs jobs_workday_board 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 jobs_workday_board, this is the rule to start with:
jobs_workday_board 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 jobs_workday_board call is checked against it from then on.
Questions about jobs_workday_board
List a Workday tenant's job board. Lists a company's public Workday (CXS) postings, paged via limit/offset. tenant, datacenter (wd1/wd3/wd5/...), and site all come from the careers URL https://{tenant}.wd5.myworkdayjobs.com/{site}. Credential-free public ATS JSON. It is categorised as a Read tool in the Crawlora MCP Server, which means it retrieves data without modifying state.
jobs_workday_board accepts 6 parameters: site, limit, offset, search, tenant, datacenter. Required: site, tenant, datacenter. 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 jobs_workday_board: 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.
jobs_workday_board 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_workday_board 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_workday_board. 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_workday_board 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