Connect Sumble to Hermes
Give Hermes governed access to Sumble’s 38 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Sumble to Hermes in four steps
Admins approve the server once. Everyone in Hermes then gets it through the same governed connection.
- 1
Add Sumble to Runlayer
Sumble 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 Sumble’s 38 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
Hermes setup guide - 3
Sign in to Sumble
Sign in the way Sumble requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Sumble from Hermes
Sumble’s approved tools appear in Hermes. Every call is checked against policy and recorded.
Tools
38 Sumble tools in Hermes
Runlayer policy decides which of these Hermes users can call.
Add contacts to list
Add people to an existing contact list.
Add organizations to list
Add organizations to an existing list.
Create contact list
Create a new contact list (people list).
Create organization list
Create a new organization list.
Find match and enrich jobs
The primary jobs tool: look up jobs by id or search the jobs corpus, and return exactly the attributes you ask for, with optional related people.
Find match and enrich organizations
Find, match, and enrich organizations in one call.
Find match and enrich people
The primary people tool: resolve people and return exactly the attributes you ask for, with optional related people and contact reveals.
Find match and enrich teams
Find the teams inside an organization and return selected attributes, related people, and job postings.
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 Sumble 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
