Skip to main content
Book a demo

Connect Workday to VS Code

Give VS Code governed access to Workday’s 60 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Book a demo VS Code setup guide

Set up

Add Workday to VS Code in four steps

Admins approve the server once. Everyone in VS Code then gets it through the same governed connection.

  1. 1

    Approve Workday in Runlayer

    Add Workday from the catalog and choose who can use it and which of its tools are allowed.

  2. 2

    Connect VS Code to Runlayer

    Runlayer’s CLI installs the Runlayer Plugin natively in VS Code; users can also add it over MCP. With direct tool listing turned on for your deployment, Workday’s 60 tools show up in VS Code’s own tool list (VS Code 1.103 or newer).

    VS Code setup guide
  3. 3

    Sign in to Workday

    Sign in the way Workday requires. Runlayer holds the credentials so they stay out of the client’s configuration.

  4. 4

    Use Workday from VS Code

    Workday’s approved tools appear in VS Code. Every call is checked against policy and recorded.

Tools

60 Workday tools in VS Code

Runlayer policy decides which of these VS Code users can call. 40 read data only and 20 can change or delete data.

  • Request time off

    Submit a time off request for a worker.

  • Get time off details

    Get paginated time off entries for a worker with optional filters.

  • Get time off entry

    Get a specific time off entry by ID.

  • Get time off balances

    Get paginated absence balances for a worker.

  • Get eligible absence types

    Get paginated absence types a worker is eligible to request.

  • Validate time off dates

    Validate one or more requested time off dates for a worker.

  • Correct time off entry

    Submit corrections for entries from one approved time off request.

  • Get leaves of absence

    Get paginated leaves of absence for a worker.

See all 60 Workday tools

Control

What Runlayer can see and stop in VS Code

Some controls apply to every client at the gateway. Others depend on what VS Code exposes to Runlayer.

  • Gateway policy (available)

    Every Workday call from VS Code passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

    Each call is recorded with the user, VS Code as the client, the tool, and the policy and scanner decisions.

  • Client hooks (available)

    Capture supported prompts, reasoning, local and MCP tool calls, responses, and scanner decisions in real time.

  • Stop a call before it runs (available)

    Runlayer can deny a tool call before VS Code runs it.

  • Block output after it runs (available)

    Runlayer can block a tool’s output before VS Code’s model sees it.

  • Redact output in place (available)

    Runlayer can mask sensitive parts of a tool’s output in VS Code and pass the rest through.

Frequently asked questions

Connect more

Find another combination