Connect Notion to Hermes
Give Hermes governed access to Notion’s 48 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Notion to Hermes in four steps
Admins approve the server once. Everyone in Hermes then gets it through the same governed connection.
- 1
Approve Notion in Runlayer
Add Notion 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 Notion’s 48 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
Hermes setup guide - 3
Sign in to Notion
Sign in the way Notion requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Notion from Hermes
Notion’s approved tools appear in Hermes. Every call is checked against policy and recorded.
Tools
48 Notion tools in Hermes
Runlayer policy decides which of these Hermes users can call. 5 read data only and 1 can change or delete data.
AI search
Notion ai search.
Check MCP next steps
Finish all Notion tool calls needed for the current request, then call at most once with no arguments.
Convert page to skill
Mark an existing Notion page as a skill without changing its content.
Create attachment
Create an attachment and upload it to Notion.
Create comment
Add a comment to a page or specific content.
Create database
Creates a new Notion database using SQL DDL syntax, or a canonical typed database for tasks, projects, or skills.
Create file upload
Create a short-lived URL for uploading one local file directly to Notion.
Create folder
Creates an empty Notion Folder.
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 Notion 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