Skip to main content
Book a demo

Connect incident.io to Claude

Give Claude governed access to incident.io’s 154 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Book a demo Claude setup guide

Set up

Add incident.io to Claude in four steps

Admins approve the server once. Everyone in Claude then gets it through the same governed connection.

  1. 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. 2

    Connect Claude to Runlayer

    Admins install the Runlayer Plugin for everyone from Claude’s admin plugin settings, or users add it themselves. With direct tool listing turned on for your deployment, incident.io’s 154 tools show up in Claude’s own tool list.

    Claude setup guide
  3. 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. 4

    Use incident.io from Claude

    incident.io’s approved tools appear in Claude. Every call is checked against policy and recorded.

Tools

154 incident.io tools in Claude

Runlayer policy decides which of these Claude 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.

See all 154 incident.io tools

Control

What Runlayer can see and stop in Claude

Some controls apply to every client at the gateway. Others depend on what Claude exposes to Runlayer.

  • Gateway policy (available)

    Every incident.io call from Claude passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

    Each call is recorded with the user, Claude as the client, the tool, and the policy and scanner decisions.

  • Anthropic inference hooks (available)

    With Claude Enterprise, Anthropic sends each governed Claude prompt to Runlayer before inference, with nothing installed on devices (Anthropic beta).

  • Compliance API import (available)

    Anthropic Compliance API imports Claude web and desktop chats for review.

  • Managed browser extension (available)

    Managed Chrome, Edge, and Firefox deployments can monitor supported web-chat activity and apply prompt-time controls where the surface permits it.

  • Stop a call before it runs (available)

    Runlayer can reject a Claude prompt before Anthropic runs it, which stops the whole request rather than one tool call.

  • Block output after it runs (available)

    Because Runlayer checks the full prompt, tool results in it can be blocked before the model sees them.

  • Redact output in place (not available)

    Anthropic Inference hooks cannot return a rewritten prompt, so Runlayer cannot mask content in Claude. The gateway still applies policy to the call.

Frequently asked questions

Connect more

Find another combination