Skip to main content
Book a demo

Connect Google Analytics to Hermes

Give Hermes governed access to Google Analytics through Runlayer, with identity, policy, scanning, and audit on every call.

Book a demo Hermes setup guide

Set up

Add Google Analytics to Hermes in four steps

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

  1. 1

    Approve Google Analytics in Runlayer

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

  2. 2

    Connect Hermes to Runlayer

    Install the Runlayer CLI so Hermes can reach Google Analytics, which runs on the user’s machine.

    Hermes setup guide
  3. 3

    Sign in to Google Analytics

    An admin adds Google Analytics credentials to Runlayer once. They never sit in the client’s configuration.

  4. 4

    Use Google Analytics from Hermes

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

Tools

Google Analytics tools in Hermes

Google Analytics reports its tools when your organization connects it, so the list depends on your deployment.

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 Google Analytics 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