Sign in Book a demo
Back to Tools
Productivity & Docs OAuth
Build Your Agent View Workday Documentation
workday logo

Workday MCP Tools for AI Agents

Let an agent check time-off balances, review request status and history, validate dates, and prepare a time-off request for the signed-in worker.

Available Tools

7 tools available in this integration

Workday.ListEligibleTimeOffTypes

List the time-off types the signed-in worker can request, with their rules.

Workday.ListTimeOffBalances

Show how much time off the signed-in worker has left, by plan.

Workday.ListTimeOffHistory

Browse the time off the signed-in worker has already logged.

Workday.ListTimeOffStatus

Show where the signed-in worker's time-off requests stand right now.

Workday.ListValidTimeOffDates

Check whether Workday accepts each date for the selected time-off type.

Workday.RequestTimeOff

Request time off for the signed-in worker, asking for a draft by default.

Workday.WhoAmI

Identify the Workday worker the connection is signed in as, and their jobs.

Why agent-optimized tools matter

Built for intent, not API schemas

Ask the agent to "check whether I have enough vacation time for next Friday and prepare the request." Arcade picks the right Workday actions without guessing worker or time-off identifiers.

Up to 100x fewer tokens

Workday reads return focused time-off types, balances, dates, history, and statuses, so the agent can decide without loading a full worker record into its context.

Complete the workflow end to end

Identify the worker, check the time-off type and balance, validate dates, draft the request, and check its status through one toolkit designed around the complete time-off task.

Make actions predictable and controlled

Arcade tools return structured results and useful errors across users and runs. Teams can apply scope restrictions, redaction, and approval policies so agents follow the same controls every time.

Securing Workday

The more capabilities agents get, the more useful they are. However, more capabilities bring more risks of undesired effects such as data loss and exfiltration.

This is why Arcade provides you with contextual rules that dictate how and when a tool is allowed to run. Arcade’s contextual access lets you govern tool visibility and behavior at every stage of execution and control who can see a tool, what inputs are allowed, and what comes back.

Learn about Contextual Access Policies

For Workday, you can implement some of these policies:

Access when tools are listed for a user
  • Hide Workday.RequestTimeOff from agents unless the roles your IDP marks as employees authorized to submit their own time-off requests are active, so an agent cannot request leave for an unauthorized worker.
Pre-execution before each tool call
  • Require human approval before Workday.RequestTimeOff runs, so an agent cannot submit time off without the worker's confirmation.
Post-execution after the tool returns
  • Redact Workday.ListTimeOffBalances results for plans containing compensation, payroll, or other restricted balance details before they reach the model.
  • Strip personal notes, medical details, and other sensitive explanations from Workday.ListTimeOffHistory results before the model sees them.
  • Redact job titles, positions, and other employment details from Workday.WhoAmI results unless the agent's task requires them.

How to use Workday with your agent

Connect Workday to an MCP client and let each worker authorize their own account. Follow the setup from connection through your first time-off workflow.

Your questions, answered

A Workday MCP server exposes Workday capabilities as structured tools that an AI agent can call through the Model Context Protocol. After a worker authorizes their account, the agent can check time-off information and submit permitted requests.

Arcade provides an integration built by Arcade with user-level OAuth, tools shaped around time-off tasks, approval workflows, redaction, and scope controls. Workday access still runs under each worker's authorization and the permissions their organization allows.

Arcade agents can identify the signed-in worker and their jobs, list eligible time-off types and rules, check balances, review time-off history and request status, validate dates, and create time-off requests as drafts by default.

Arcade requires the Workday permissions needed for the actions you enable, subject to the signed-in worker's access in their Workday organization. Read-only workflows need access to the relevant worker and time-off records; requesting time off also requires permission to submit that request.

Yes. Each worker authorizes their own Workday account through OAuth. Actions run under that worker's authorization, so the agent can access only the Workday account and permissions they approved.

Yes. Contextual Access policies can require human approval before an agent submits a Workday time-off request. The call proceeds only after the policy's conditions have been satisfied.

Arcade proxies Workday API calls and does not persist Workday content as part of normal tool execution. Credentials are brokered and stored encrypted at rest, and the model never receives them.

Any framework or client that can connect to Arcade's MCP gateway or tool APIs works, including LangChain, OpenAI Agents, CrewAI, Claude Desktop, Claude Code, Cursor, Visual Studio Code, Microsoft Copilot Studio, and GitHub Copilot.

Arcade refreshes access while the worker's Workday authorization remains valid. If it is revoked, rotated, or can no longer be refreshed, calls stop until the worker reconnects Workday.

Workday API rate limits, tenant policies, and any limits on the connected Workday environment still apply to calls through Arcade. Arcade does not remove those restrictions, so high-volume workflows should account for throttling and retry behavior.

Ready to actually ship your agent?

Connect your agent to Workday with managed OAuth, agent-optimized tools and approval controls for consequential actions.

Build Your Agent Read the Workday Quickstart