Connect incident.io to GitHub Copilot
Give GitHub Copilot 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 in four steps
Admins approve the server once. Everyone in GitHub Copilot 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 to Runlayer
GitHub Copilot gets connector tools through the Runlayer Plugin, and reaches incident.io’s 154 tools through the plugin’s search and execute tools.
GitHub Copilot 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
incident.io’s approved tools appear in GitHub Copilot. Every call is checked against policy and recorded.
Tools
154 incident.io tools in GitHub Copilot
Runlayer policy decides which of these GitHub Copilot 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
Some controls apply to every client at the gateway. Others depend on what GitHub Copilot exposes to Runlayer.
Gateway policy (available)
Every incident.io call from GitHub Copilot 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 as the client, the tool, and the policy and scanner decisions.
Native enforcement adapter (not available)
Runlayer has no device-side adapter for GitHub Copilot yet, so control happens at the gateway.
Frequently asked questions
Connect more