Skip to main content
Book a demo

Connect AWS Knowledge to Hermes

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

Book a demo Hermes setup guide

Set up

Add AWS Knowledge to Hermes in four steps

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

  1. 1

    Add AWS Knowledge to Runlayer

    AWS Knowledge isn’t in the Runlayer catalog yet, so an admin adds it by its MCP server URL.

    Adding a connector manually
  2. 2

    Connect Hermes to Runlayer

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

    Hermes setup guide
  3. 3

    Sign in to AWS Knowledge

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

  4. 4

    Use AWS Knowledge from Hermes

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

Tools

5 AWS Knowledge tools in Hermes

Runlayer policy decides which of these Hermes users can call.

  • Get regional availability

    AWS resource availability per region.

  • List regions

    Retrieve a list of all AWS regions.

  • Read documentation

    Fetch full AWS doc pages as markdown.

  • Retrieve skill

    Retrieve an AWS skill (workflows, references).

  • Search documentation

    AWS docs search.

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 AWS Knowledge 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