# Dayforce MCP server for HR teams

> A Dayforce MCP server for HR teams needs one rule up front: generalists read, HRIS admins write. Here is how to set that split up in Claude or ChatGPT.

**TL;DR** Elaichi's Dayforce connector puts 310 Dayforce tools behind one MCP address. HR generalists get the read tools through a role restriction, and only the HRIS admins keep the tools that hire, change pay data or delete records. The Dayforce connection runs on one Dayforce credential, so Dayforce's own role limits the data and Elaichi's restrictions limit the tools.

## How does a Dayforce MCP server for HR teams stay read-only for generalists?

Yes, it can. Connect Dayforce in Elaichi with its API key and add https://api.elaichi.ai/mcp in Claude, ChatGPT, Cursor or Microsoft Copilot. Then hold the HR generalist role to the 11 named read tools below with a restriction on the role.

An HR operations desk answers the same questions all day. Who reports to this manager. When does the new hire start. How many vacation hours are left. A Dayforce MCP server for HR teams puts those answers in one chat sentence. MCP (Model Context Protocol) is the standard way an AI assistant calls tools in other apps. The [Dayforce connector](/connectors/ceridiandayforce/) carries 310 tools, and the risk is in the more than 170 that create, update or delete.

## What does Dayforce's own API security look like?

Dayforce controls API access through a role on the account making the call. Its guide says that account needs the Web Services feature on its default role, with Read Data as the minimum sub-feature (checked November 2026, [Dayforce's Web Services role feature guide](https://help.dayforce.com/r/documents/Dayforce-RESTful-Web-Services-Developer-Guide/Add-the-Web-Services-Role-Feature)). The REST services use HTTP basic authentication, so each request carries credentials (checked November 2026, [Dayforce's authentication guide](https://help.dayforce.com/r/documents/Dayforce-RESTful-Web-Services-Developer-Guide/Authentication)). Basic authentication sends a user ID and password in a header and relies on a secure channel such as TLS (checked November 2026, [RFC 7617](https://datatracker.ietf.org/doc/html/rfc7617)).

The second control matters more for HR. Dayforce filters returned data by field-level access and by access authorizations on the default role. Both must pass. Data that fails is left out, and Dayforce omits the property or sets it to null instead of raising an error (checked November 2026, [Dayforce's data authorization guide](https://help.dayforce.com/r/documents/Dayforce-RESTful-Web-Services-Developer-Guide/Data-Authorization-and-Filtering)). Many Dayforce read tools in Elaichi say the same in their descriptions.

Two things follow for the desk. The Dayforce role is the only fence that reaches inside a record to single fields. And a null in an answer does not prove the value is empty, so tell the team to read a blank as "not visible to this account" first.

## Whose Dayforce account runs each call?

One account runs all of them. In Elaichi, every call through a connection uses the credential that connection was made with, whoever is calling. A connection shared with the HR team runs each teammate's call on its owner's Dayforce sign-in.

For a flat HR desk that is the right shape. An HRIS admin connects Dayforce with a web services account whose role is already trimmed to what generalists may see. They share the connection so the team can run tools through it. Every generalist gets the same data ceiling, set in Dayforce, and nobody holds an API credential.

Where Dayforce roles differ by person, such as managers who see only their own reports, have each person connect their own Dayforce account instead. Dayforce then applies that person's role. The price is many credentials to create and to retire.

If the credential is ever in doubt, revoking a share or disconnecting an account takes effect on the caller's next call, so the stop is quick. Separately, when the HRIS admin who owns the connection is leaving, transfer it to someone who stays in the offboarding step. A shared connection that offboarding does not transfer is left in place, untouched.

## Which Dayforce tools should HR generalists reach?

These 11 read tools answer the desk questions, and they are the ones to name in the restriction:

| Question | Tools |
|---|---|
| Who is this person? | list_all_ceridiandayforce_employees, get_single_ceridiandayforce_employee_by_id |
| Who do they report to? | list_all_ceridiandayforce_employee_managers, list_all_ceridiandayforce_employee_work_assignment_managers |
| Where do they sit? | list_all_ceridiandayforce_departments, list_all_ceridiandayforce_org_units, list_all_ceridiandayforce_positions |
| What is their status? | list_all_ceridiandayforce_employment_statuses, list_all_ceridiandayforce_employee_employment_statuses |
| What time off is left? | list_all_ceridiandayforce_employee_balance_periods, get_single_ceridiandayforce_time_away_from_work_by_id |

Some other reads are sensitive even though they only read. list_all_ceridiandayforce_direct_deposits lists account numbers and bank names. list_all_ceridiandayforce_dependents_beneficiaries lists Social Security numbers. get_single_ceridiandayforce_confidential_identification_by_id and list_all_ceridiandayforce_health_wellness_details are what they sound like. list_all_ceridiandayforce_earning_statements returns pay statements. Keep all of them off the generalist role. Give them to a payroll or benefits role if one needs them.

## Which Dayforce tools stay with the HRIS admins?

Anything that creates, updates or deletes belongs to the people accountable for the system of record. create_a_ceridiandayforce_employee hires someone, and update_a_ceridiandayforce_employee_by_id changes a record. The bulk_update tools patch whole families of records at once, from work assignments and employment statuses to tax setups. create_a_ceridiandayforce_payroll_garnishment creates or updates a garnishment.

Dayforce's delete tools are not all called delete_. The catalog has ceridiandayforce_employee_punches_bulk_delete and ceridiandayforce_sso_accounts_bulk_delete. It also has create_a_ceridiandayforce_documents_delete, which deletes a batch of documents by GUID, and ceridiandayforce_payroll_delete_payroll_elections_bulk_update, which deletes payroll elections through a PATCH. A rule that names only tools starting with delete_ would catch none of the four, so read tool descriptions before calling a role safe.

Some write tools take a validate-only flag. The create HR incident and garnishment descriptions both mention isValidateOnly, which checks a request without saving it. Admins can use it as a habit. Elaichi does not enforce it.

## Allow rule or block rules for the HR generalist role?

Holding a role to an app's reads takes one of two shapes. One is an allow rule naming those reads, plus allow rules for every other app the role uses. The other is block rules naming every tool on the app that is not a read. With an allow rule, once a role carries any allow rule, every connector and tool none of its allow rules names is blocked for that role. With block rules, a layer with only block rules has no allowlist, so everything it does not block passes it.

The test is the size of the non-read list. Block rules suit an app with few non-read tools you can list in full. Dayforce has more than 170, so the HR generalist role takes an allow rule naming the 11 reads above. Add whole-connector allow rules for each other app the role uses, such as Slack or Google Drive, or the generalists lose them when the Dayforce rule saves.

In Elaichi, restriction targets are role or user only; the organization default is the absence of a rule, which means allow everything, so the rule goes on the generalist role itself. A rule aimed at a member can only narrow what their role allows, and never replaces or loosens a role rule, which lets you narrow one person without editing the role.

## What happens when a generalist hits a limit, and what is logged?

A generalist may ask for a tool the rule withholds. A restricted tool is left out of the tools Elaichi offers a client and cannot be called. Search still names it, flagged restricted, with no schema. The generalist can file an access request from the client, and an admin decides it in the Elaichi console under Governance, then Access requests. A role change takes effect in about two minutes.

For HR, the audit log is the answer to "who looked up this record". It writes one entry for each connected-tool call that reaches execution (a call refused earlier writes none). Each entry names the person, the Dayforce tool, the connection and the AI client. The trail records the one path argument that names the object, as the target id, and nothing else about the arguments. It does not copy the returned fields, so the log is not a second store of employee data. Elaichi keeps 90 days of history, and for longer, export to your own Datadog comes with the Black plan.

## How does an HR teammate connect Claude or ChatGPT?

Each person adds https://api.elaichi.ai/mcp in their AI client and signs in through the browser. They approve their own grant, which names the organization and the person. The address is the same for everyone, so there is nothing per-team to copy.

No checkbox on that sign-in screen holds the client to reading Dayforce. "Use your connected apps" lets the client run every kind of Dayforce tool, writes and deletes included, so the role restriction does the holding. For a second fence, choose "Only the ones I pick" and pick a toolbox of read tools.

Over MCP, Elaichi does not stop a write to ask first. A hire or a pay change typed into chat runs once the role allows it. If the desk wants a confirm step, turn it on in Claude or ChatGPT. In the client, connected tools are never listed one by one, however few there are, so the assistant searches for a Dayforce tool and then runs it.

## Is this worth it for a one-person HRIS team?

Not always. If one HRIS admin is the only person who will ever ask Dayforce questions from an AI client, skip the roles. Connect it under that admin's own credential and keep the connection private. The audit log still shows what ran.

The restriction earns its place when a desk of generalists shares one Dayforce account and someone has to show who could change what. For that case, the [Dayforce connector page](/connectors/ceridiandayforce/) lists every tool. The [connector catalog](/connectors/) covers the other 900+ connectors. [Gusto and Claude for an HR team](/blog/hr-team-claude-gusto-payroll/) shows the same split in another HR app.

## FAQ

### Can an HR generalist use Dayforce through an AI client without being able to change records?

Yes, if the role carries an allow rule that names only read tools. In Elaichi, no consent checkbox makes a connected app read-only, because "Use your connected apps" runs every tier of tool. The hold comes from a restriction on the role, or from approving the connection with toolboxes that contain only read tools.

### Why does a Dayforce field come back empty through Elaichi?

Dayforce leaves out fields the account behind the connection may not see. Its documentation says data is filtered by field-level and access authorizations on the default role, and that unauthorized properties are not present on the response (checked November 2026, https://help.dayforce.com/r/documents/Dayforce-RESTful-Web-Services-Developer-Guide/Data-Authorization-and-Filtering). An empty field can mean the role cannot see it, not that no value exists.

### Does each HR teammate need their own Dayforce account to use the connector?

Not for the connector to work. Every call through a connection in Elaichi uses the credential that connection was made with, whoever is calling. A teammate with their own Dayforce account can connect it themselves, and then Dayforce applies their own role to their calls.

### How fast does a change to the HR generalist role reach their AI client?

Within about two minutes. A change to a role, a restriction or a team membership reaches Claude, ChatGPT and the console on that schedule. Removing or suspending a member is faster: their MCP clients stop on the next call.

## Read next

- [Keep payroll data in HR with Gusto in Claude](/blog/hr-team-claude-gusto-payroll/) — Gusto in Claude runs on Gusto's own MCP server. One admin connects it in Elaichi, HR gets a Gusto-only toolbox, and roles decide who reaches which tool.
- [Keep BambooHR salary data out of AI assistants](/blog/hr-team-bamboohr-salary-data/) — Two layers keep BambooHR salary data away from Claude and ChatGPT: the access level behind the API key, and an allow rule per role in Elaichi.
- [Restrict one AI tool or the whole app? Six cases](/blog/per-tool-vs-per-app-restrictions/) — Restrict one AI tool when a role needs part of an app, and block the whole app when it needs none of it. Six cases, and what new tools do to each rule.
