Connect Omni to Claude
Give Claude governed access to Omni’s 25 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Omni to Claude in four steps
Admins approve the server once. Everyone in Claude then gets it through the same governed connection.
- 1
Add Omni to Runlayer
Omni isn’t in the Runlayer catalog yet, so an admin adds it by its MCP server URL.
Adding a connector manually - 2
Connect Claude to Runlayer
Admins install the Runlayer Plugin for everyone from Claude’s admin plugin settings, or users add it themselves. With direct tool listing turned on for your deployment, Omni’s 25 tools show up in Claude’s own tool list.
Claude setup guide - 3
Sign in to Omni
Sign in the way Omni requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Omni from Claude
Omni’s approved tools appear in Claude. Every call is checked against policy and recorded.
Tools
25 Omni tools in Claude
Runlayer policy decides which of these Claude users can call.
Ask Omni
Starts the full Omni AI agent on an open-ended or multi-step analytical question and returns immediately with a 'jobId' — it does NOT wait for or return the answer, which is retrieved separately once…
Cancel job
Stops a job started by askOmni.
Check dashboard download
Polls a dashboard download started by startDashboardDownload.
Check status
Checks on a job started by askOmni and returns quickly.
Fetch dashboard download
Returns the png a completed dashboard download produced — the job from startDashboardDownload once checkDashboardDownload reports it "complete" — as an image you can look at, after a text block with…
Get app
Alpha — the app content shape may change without a deprecation cycle.
Get app draft
Alpha — the app content shape may change without a deprecation cycle.
Get data
Gets data by generating and executing a query from natural language.
Control
What Runlayer can see and stop in Claude
Some controls apply to every client at the gateway. Others depend on what Claude exposes to Runlayer.
Gateway policy (available)
Every Omni call from Claude passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Claude as the client, the tool, and the policy and scanner decisions.
Anthropic inference hooks (available)
With Claude Enterprise, Anthropic sends each governed Claude prompt to Runlayer before inference, with nothing installed on devices (Anthropic beta).
Compliance API import (available)
Anthropic Compliance API imports Claude web and desktop chats for review.
Managed browser extension (available)
Managed Chrome, Edge, and Firefox deployments can monitor supported web-chat activity and apply prompt-time controls where the surface permits it.
Stop a call before it runs (available)
Runlayer can reject a Claude prompt before Anthropic runs it, which stops the whole request rather than one tool call.
Block output after it runs (available)
Because Runlayer checks the full prompt, tool results in it can be blocked before the model sees them.
Redact output in place (not available)
Anthropic Inference hooks cannot return a rewritten prompt, so Runlayer cannot mask content in Claude. The gateway still applies policy to the call.
Frequently asked questions
Connect more