Home / Servers / DigitalOcean API / harness_post_session_hitl
ResolveHITL records the user's decision on a pending HITL request.
An MCP tool from the DigitalOcean API server, hosted on mcp.hjlabs.in.
ResolveHITL records the user's decision on a pending HITL request. harness-api forwards the decision into the owning microVM via the inbound runtime.v1.OHR.ResolveHITL RPC (dialed through the guest-fronting proxy), which unblocks the gated agent action. The… [POST /v2/agents/sessions/{session_id}/hitl/{request_id}]
Name on the gateway: digitalocean_api__harness_post_session_hitl · may change things.
Parameters
| Name | Type | Description |
|---|---|---|
session_id required | string | The session UUID. |
request_id required | string | The HITL request identifier. |
outcome required | HITL_OUTCOME_UNSPECIFIED | HITL_OUTCOME_APPROVE | HITL_OUTCOME_REJECT | HITL_OUTCOME_DEFER | HITLOutcome is the user's decision on a HITL request. DEFER backs off this… |
reason | string | Optional free-text reason. Captured in the audit trail; not interpreted. |
source | RESOLUTION_SOURCE_UNSPECIFIED | RESOLUTION_SOURCE_INLINE_KEYSTROKE | RESOLUTION_SOURCE_OUT_OF_BAND | How a HITL resolution was triggered. Defaults to RESOLUTION_SOURCE_OUT_OF_BAND… |
How to call it
Through the Smart Gateway, any client can run it by name with call_tool, or let the gateway find it with search_tools:
{
"name": "digitalocean_api__harness_post_session_hitl",
"arguments": {
"session_id": "…",
"request_id": "…",
"outcome": "…"
}
}Or connect the DigitalOcean API server directly, which lists 874 tools including this one:
claude mcp add --transport http hj-digitalocean-api https://mcp.hjlabs.in/mcp/digitalocean-api \
--header "Authorization: Bearer YOUR_API_KEY"Try asking
Use the resolvehitl records the user's decision on a pending hitl request. tool with session_id set to ….