Connect Chronosphere to Warp
Give Warp governed access to Chronosphere’s 31 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Chronosphere to Warp in four steps
Admins approve the server once. Everyone in Warp then gets it through the same governed connection.
- 1
Add Chronosphere to Runlayer
Chronosphere isn’t in the Runlayer catalog yet, so an admin adds it by its MCP server URL.
Adding a connector manually - 2
Connect Warp to Runlayer
Users add the Runlayer Plugin to Warp by following Runlayer’s setup guide. Warp reaches Chronosphere’s 31 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
Warp setup guide - 3
Sign in to Chronosphere
Sign in the way Chronosphere requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Chronosphere from Warp
Chronosphere’s approved tools appear in Warp. Every call is checked against policy and recorded.
Tools
31 Chronosphere tools in Warp
Runlayer policy decides which of these Warp users can call.
Get dashboard
Get dashboards resource
Get drop rule
Get drop-rules resource
Get events metadata
List properties you can query on events
Get log
Get a full log message by its ID.
Get log histogram
Get histogram of logs from a given query
Get mapping rule
Get mapping-rules resource
Get monitor
Get monitors resource
Get notification policy
Get notification-policies resource
Control
What Runlayer can see and stop in Warp
Some controls apply to every client at the gateway. Others depend on what Warp exposes to Runlayer.
Gateway policy (available)
Every Chronosphere call from Warp passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Warp as the client, the tool, and the policy and scanner decisions.
Native enforcement adapter (not available)
Runlayer has no device-side adapter for Warp yet, so control happens at the gateway.
Frequently asked questions
Connect more