Connect AirOps to Claude
Give Claude governed access to AirOps’s 100 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add AirOps to Claude in four steps
Admins approve the server once. Everyone in Claude then gets it through the same governed connection.
- 1
Approve AirOps in Runlayer
Add AirOps from the catalog and choose who can use it and which of its tools are allowed.
- 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, AirOps’s 100 tools show up in Claude’s own tool list.
Claude setup guide - 3
Sign in to AirOps
Sign in the way AirOps requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use AirOps from Claude
AirOps’s approved tools appear in Claude. Every call is checked against policy and recorded.
Tools
100 AirOps tools in Claude
Runlayer policy decides which of these Claude users can call.
Accept opportunity
Accept pending opportunities for a campaign and add them to the campaign action grid.
Add AEO region
Add a region (ISO alpha-2 country code) to a Brand Kit's configured AEO regions.
Add grid column
Add a new column to a grid table.
Analytics chart
Query analytics data and display it as an interactive chart.
Automated feedback report
AirOps only feedback tool.
Bulk update AEO prompt tags
Apply a single tag operation (add or remove) to a batch of AEO prompts in one Brand Kit, atomically.
Bulk update AEO prompt topics
Reassign a batch of AEO prompts to an existing topic in one Brand Kit.
Commit AEO prompt assignments
Commit the current prompt-assignment draft for a Brand Kit to live.
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 AirOps 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