Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.igrisecurity.com/llms.txt

Use this file to discover all available pages before exploring further.

​
Sessions

Agent sessions are automatically created when an MCP client begins making tool calls through the Igris gateway. They provide a grouping mechanism for related tool calls and a kill switch for immediate control.

​
How Sessions Work

When the proxy receives a tool call, Igris checks for an active session for that organization + connection combination. If none exists, one is created automatically. Each session tracks:
  • Organization — which org owns this session
  • Connection — which connection the calls are routed through
  • Status — active or suspended
  • Tool call count — total number of calls in this session
  • Created at / Updated at — timestamps

​
Viewing Sessions

In the dashboard, go to Governance → Sessions to see all active and suspended sessions. Each session shows:
  • Connection name
  • Tool call count
  • Duration
  • Current status

​
Kill Switch

The kill switch lets you instantly suspend a session. When suspended:
  • All incoming tool calls for that session return a 503 Session Suspended error
  • The upstream MCP server receives no further requests
  • An audit event is logged recording the suspension
  • SSE event is broadcast to dashboard clients

​
Suspending a Session

Click the Suspend button on any active session in the dashboard.

​
Resuming a Session

Click Resume on a suspended session in the dashboard.

​
Use Cases

  • Incident response — immediately halt a misbehaving agent without restarting infrastructure
  • Maintenance windows — suspend sessions during database maintenance
  • Investigation — pause activity while reviewing anomaly alerts
  • Cost control — stop a runaway agent racking up API costs

​
Session Deduplication

Igris prevents duplicate sessions for the same org + connection combination. If a session already exists and is active, new tool calls join that session rather than creating a new one. This keeps the audit trail clean and the kill switch effective.