---
title: "Api Disable Host"
method: POST
path: "/dashboard/api/hosts/{host_id}/disable"
tags: ["dashboard"]
---

# Api Disable Host

`POST /dashboard/api/hosts/{host_id}/disable`

## Request

- Base URL: `https://mcp.sentinelx.app` (the document declares no server; this is the origin it was published from)
- URL: `https://mcp.sentinelx.app/dashboard/api/hosts/{host_id}/disable`
- Auth: none declared

Disable a host: mark it as blocked AND close the active session.

Disable is persistent — once disabled, the agent's reconnect
attempts are rejected at handshake until the user re-enables.
The host stays visible in the dashboard with a "Disabled" badge.

Does NOT revoke the agent's identity_token. If the user wants a
hard revoke (e.g. server compromised, token leaked), that's a
separate operation (not implemented yet).

## Path parameters

- `host_id` string, required

## Cookies

- `sentinelx_dash_session` string, nullable

## Request body

- DisableBody: Body for disable. `reason` is optional free text the user can leave for themselves — appears in the dashboard next to the badge.
  - `reason` string

## Response `200`

Successful Response

- unknown

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/sentinelx/apis/sentinelx-hub.md) · [All operations](https://skmtc.dev/sentinelx/apis/sentinelx-hub/llms.txt) · [OpenAPI document](https://skmtc.dev/sentinelx/apis/sentinelx-hub/revisions/d1f84924795e?raw)