Connect Ashby ATS to Hermes
Give Hermes governed access to Ashby ATS’s 16 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Ashby ATS to Hermes in four steps
Admins approve the server once. Everyone in Hermes then gets it through the same governed connection.
- 1
Approve Ashby ATS in Runlayer
Add Ashby ATS from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect Hermes to Runlayer
Users add the Runlayer Plugin to Hermes by following Runlayer’s setup guide. Hermes reaches Ashby ATS’s 16 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
Hermes setup guide - 3
Sign in to Ashby ATS
Each user signs in to Ashby ATS with OAuth. Runlayer keeps the tokens out of the client’s configuration.
- 4
Use Ashby ATS from Hermes
Ashby ATS’s approved tools appear in Hermes. Every call is checked against policy and recorded.
Tools
16 Ashby ATS tools in Hermes
Runlayer policy decides which of these Hermes users can call.
Add note to candidate
Add a note to a candidate's profile.
Change application stage
Move an application to a different interview stage.
Consider candidate for job
Create a new application for a candidate on a specific job.
Create candidate
Create a new candidate record in Ashby with a name and optional contact information.
Describe object fields
Look up filterable fields for a given object type.
Filter records
Filter records of a given object type using a structured JSON filter.
Get candidate
Fetch details about one or more candidates.
Get interview details
Get a detailed interview briefing for a specific Ashby interview event.
Control
What Runlayer can see and stop in Hermes
Some controls apply to every client at the gateway. Others depend on what Hermes exposes to Runlayer.
Gateway policy (available)
Every Ashby ATS call from Hermes passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Hermes 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 Hermes runs it.
Block output after it runs (available)
Runlayer can block a tool’s output in Hermes and show a message in its place.
Redact output in place (not available)
Hermes cannot take masked output, so Runlayer can block a tool’s output but not mask it. The gateway still applies policy to the call.
In Hermes
- Hermes can replace blocked tool output with a message, but its after-call event is for monitoring only.
Frequently asked questions
Connect more
