Connect Fullstory to Hermes
Give Hermes governed access to Fullstory’s 30 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Fullstory to Hermes in four steps
Admins approve the server once. Everyone in Hermes then gets it through the same governed connection.
- 1
Add Fullstory to Runlayer
Fullstory isn’t in the Runlayer catalog yet, so an admin adds it by its MCP server URL.
Adding a connector manually - 2
Connect Hermes to Runlayer
Users add the Runlayer Plugin to Hermes by following Runlayer’s setup guide. Hermes reaches Fullstory’s 30 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
Hermes setup guide - 3
Sign in to Fullstory
Sign in the way Fullstory requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Fullstory from Hermes
Fullstory’s approved tools appear in Hermes. Every call is checked against policy and recorded.
Tools
30 Fullstory tools in Hermes
Runlayer policy decides which of these Hermes users can call.
Build funnel
Build a Fullstory funnel from a natural-language description.
Build journey
Build a FullStory journey from a natural-language description.
Build metric
Build a Fullstory metric from a natural language description.
Build segment
Build a Fullstory segment from a natural language description.
Compute funnel
Execute a saved funnel and return per-step counts and conversion rates.
Compute journey
Execute a journey and return the computed step-by-step breakdown.
Compute metric
Execute a metric and return the computed result.
Discover groups
Finds the top frustration and error groups across recorded data for the org.
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 Fullstory 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