Connect incident.io to VS Code
Give VS Code 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 VS Code in four steps
Admins approve the server once. Everyone in VS Code 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 VS Code to Runlayer
Runlayer’s CLI installs the Runlayer Plugin natively in VS Code; users can also add it over MCP. With direct tool listing turned on for your deployment, incident.io’s 154 tools show up in VS Code’s own tool list (VS Code 1.103 or newer).
VS Code 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 VS Code
incident.io’s approved tools appear in VS Code. Every call is checked against policy and recorded.
Tools
154 incident.io tools in VS Code
Runlayer policy decides which of these VS Code 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 VS Code
Some controls apply to every client at the gateway. Others depend on what VS Code exposes to Runlayer.
Gateway policy (available)
Every incident.io call from VS Code passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, VS Code 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 before VS Code runs it.
Block output after it runs (available)
Runlayer can block a tool’s output before VS Code’s model sees it.
Redact output in place (available)
Runlayer can mask sensitive parts of a tool’s output in VS Code and pass the rest through.
Frequently asked questions
Connect more