Skip to main content
Book a demo

Connect CrowdStrike Falcon to Hermes

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

Book a demo Hermes setup guide

Set up

Add CrowdStrike Falcon to Hermes in four steps

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

  1. 1

    Approve CrowdStrike Falcon in Runlayer

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

    Hermes setup guide
  3. 3

    Sign in to CrowdStrike Falcon

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

  4. 4

    Use CrowdStrike Falcon from Hermes

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

Tools

169 CrowdStrike Falcon tools in Hermes

Runlayer policy decides which of these Hermes users can call.

  • Add case alert evidence

    Attach alert evidence to an existing case.

  • Add case event evidence

    Attach LogScale event evidence to an existing case.

  • Add IOC

    Create one or more custom IOCs.

  • Aggregate case access tags

    Count case access tags grouped by a field.

  • Aggregate case file details

    Report the files attached to cases, grouped and counted by a field.

  • Aggregate case notification groups

    Count case notification groups grouped by a field.

  • Aggregate case slas

    Count case SLA definitions grouped by a field.

  • Aggregate case templates

    Count case templates grouped by a field.

See all 169 CrowdStrike Falcon 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 CrowdStrike Falcon 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