Skip to main content
Book a demo

Connect Jam to Hermes

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

Book a demo Hermes setup guide

Set up

Add Jam to Hermes in four steps

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

  1. 1

    Approve Jam in Runlayer

    Add Jam 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 Jam’s 15 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.

    Hermes setup guide
  3. 3

    Sign in to Jam

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

  4. 4

    Use Jam from Hermes

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

Tools

15 Jam tools in Hermes

Runlayer policy decides which of these Hermes users can call. 13 read data only.

  • Get Jam bug report details and metadata

    Retrieve comprehensive metadata and details for a specific Jam bug report.

  • Get network activity and HTTP request logs

    Extract network activity logs captured during the Jam session.

  • Get browser console output and javascript logs

    Retrieve browser console output captured during the Jam session.

  • Get user interaction timeline and events

    Access the complete timeline of user interactions captured in the Jam.

  • Get custom Jam metadata

    Retrieve custom metadata set via the jam.metadata() SDK.

  • Get visual screenshots and image attachments

    Retrieve visual screenshots and image attachments from screenshot-type Jams.

  • Analyze video recording

    Extract user intents from a Jam recording.

  • Get video transcript

    Retrieve the speech transcript (captions) from a video Jam recording in WebVTT format with timestamps.

See all 15 Jam 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 Jam 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