Skip to main content
Book a demo

Connect Lever to Hermes

Give Hermes governed access to Lever’s 13 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Book a demo Hermes setup guide

Set up

Add Lever to Hermes in four steps

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

  1. 1

    Approve Lever in Runlayer

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

  2. 2

    Connect Hermes to Runlayer

    Users add the Runlayer Plugin to Hermes by following Runlayer’s setup guide. Hermes reaches Lever’s 13 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.

    Hermes setup guide
  3. 3

    Sign in to Lever

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

  4. 4

    Use Lever from Hermes

    Lever’s approved tools appear in Hermes. Every call is checked against policy and recorded.

Tools

13 Lever tools in Hermes

Runlayer policy decides which of these Hermes users can call. 8 read data only and 1 can change or delete data.

  • List opportunities

    List opportunities (candidates) in Lever with optional filters.

  • Get opportunity

    Get detailed information about a specific opportunity (candidate) by ID.

  • Update stage

    Move a candidate to a different pipeline stage.

  • Archive opportunity

    Archive a candidate with a specific reason.

  • Add tags

    Add tags to an opportunity (candidate).

  • Remove tags

    Remove tags from an opportunity (candidate).

  • List postings

    List job postings in Lever with optional filters.

  • Get posting

    Get detailed information about a specific job posting by ID.

See all 13 Lever tools

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 Lever 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

Find another combination