Connect incident.io to GitHub Copilot CLI
Give GitHub Copilot CLI governed access to incident.io’s 154 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add incident.io to GitHub Copilot CLI in four steps
Admins approve the server once. Everyone in GitHub Copilot CLI then gets it through the same governed connection.
- 1
Approve incident.io in Runlayer
Add incident.io from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect GitHub Copilot CLI to Runlayer
Users add the Runlayer Plugin to GitHub Copilot CLI by following Runlayer’s setup guide. GitHub Copilot CLI reaches incident.io’s 154 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
GitHub Copilot CLI setup guide - 3
Sign in to incident.io
Sign in the way incident.io requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use incident.io from GitHub Copilot CLI
incident.io’s approved tools appear in GitHub Copilot CLI. Every call is checked against policy and recorded.
Tools
154 incident.io tools in GitHub Copilot CLI
Runlayer policy decides which of these GitHub Copilot CLI users can call. 26 read data only and 9 can change or delete data.
Action convert
Convert an incident action into a follow-up.
Create action
Create an action on an incident.
Delete action
Delete an incident action.
List action
List incident actions with optional filters and pagination.
Update action
Update an existing incident action.
Alert attach
Attach an existing alert to an incident, marking it as related.
Alert create incident
Declare a new incident for one or more alerts, attaching them to it as related.
Alert detach
Detach an alert from an incident, marking it as unrelated.
Control
What Runlayer can see and stop in GitHub Copilot CLI
Some controls apply to every client at the gateway. Others depend on what GitHub Copilot CLI exposes to Runlayer.
Gateway policy (available)
Every incident.io call from GitHub Copilot CLI passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, GitHub Copilot CLI 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 or permission request before GitHub Copilot CLI runs it.
Block output after it runs (available)
Runlayer can block a tool’s output before GitHub Copilot CLI’s model sees it.
Redact output in place (available)
Runlayer can mask sensitive parts of a successful tool’s output in GitHub Copilot CLI and pass the rest through.
In GitHub Copilot CLI
- When a tool fails, Runlayer records the error but cannot replace it.
Frequently asked questions
Connect more