Connect incident.io to Codex
Give Codex 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 Codex in four steps
Admins approve the server once. Everyone in Codex 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 Codex to Runlayer
Runlayer’s CLI adds the Runlayer Plugin to Codex’s local plugin marketplace, and users then enable it in Codex. With direct tool listing turned on for your deployment, incident.io’s 154 tools show up in Codex’s own tool list (Codex 0.122 or newer, installed through the Runlayer CLI).
Codex 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 Codex
incident.io’s approved tools appear in Codex. Every call is checked against policy and recorded.
Tools
154 incident.io tools in Codex
Runlayer policy decides which of these Codex 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 Codex
Some controls apply to every client at the gateway. Others depend on what Codex exposes to Runlayer.
Gateway policy (available)
Every incident.io call from Codex passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Codex 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 Codex runs it.
Block output after it runs (available)
Runlayer can block a tool’s output before Codex’s model sees it.
Redact output in place (not available)
Codex cannot take masked output, so Runlayer can block a tool’s output but not mask it. The gateway still applies policy to the call.
Frequently asked questions
Connect more