Connect Skyvern to Hermes
Give Hermes governed access to Skyvern’s 77 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Skyvern to Hermes in four steps
Admins approve the server once. Everyone in Hermes then gets it through the same governed connection.
- 1
Approve Skyvern in Runlayer
Add Skyvern from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect Hermes to Runlayer
Users add the Runlayer Plugin to Hermes by following Runlayer’s setup guide. Hermes reaches Skyvern’s 77 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
Hermes setup guide - 3
Sign in to Skyvern
Sign in the way Skyvern requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Skyvern from Hermes
Skyvern’s approved tools appear in Hermes. Every call is checked against policy and recorded.
Tools
77 Skyvern tools in Hermes
Runlayer policy decides which of these Hermes users can call. 34 read data only and 11 can change or delete data.
Create browser session
Create a new browser session to start interacting with websites.
Close browser session
Close a browser session when you're done.
List browser sessions
List all active browser sessions.
Get browser session
Get details about a specific browser session -- status, timeout, availability.
Connect to browser session
Connect to an existing browser -- a cloud session by ID or any browser via CDP URL.
Perform browser action (ai)
Perform actions on a page by describing what to do in plain English.
Extract data from page (ai)
Extract structured data from the current page using AI with screenshots and a dedicated extraction LLM.
Validate page condition (ai)
Check if a condition is true on the current page — cheapest AI option for yes/no questions.
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 Skyvern 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
