get_v1_agents_sessions_id_control
DrainSessionControl returns the steering commands (pause/resume/stop/message) recorded against the caller's own session that are newer than the cursor, oldest first, with the cursor to poll from…
DrainSessionControl returns the steering commands (pause/resume/stop/message)
recorded against the caller's own session that are newer than the cursor,
oldest first, with the cursor to poll from next. It is how a locally started
hanzo code session — which is not task-backed, so nothing forwards its
commands to an execution engine — consumes what the dashboard posted. Read-only
and bounded at 200 per poll, so a steady poll is cheap and an applied command is
never redelivered.
| Tool | get_v1_agents_sessions_id_control |
| Door | https://api.hanzo.ai/v1/mcp |
| Method | tools/call (JSON-RPC 2.0) |
| Arguments | 2, 1 required |
| Operation | GET /v1/agents/sessions/{id}/control |
| Product | agents |
Arguments
| Field | Type | Required | Default | Values | Description |
|---|---|---|---|---|---|
after | integer | — | — | — | After is the last seq this poller applied; only commands newer than it come back. Absent or negative reads as 0, which drains from the beginning. |
id | string | yes | — | — | ID is the session whose commands are being drained, from the path. |
tools/list declares a type and a description for each field and nothing further. The Required column is taken from GET /v1/agents/sessions/{id}/control, the operation this tool dispatches to — the same declaration the REST API validates against. A — means neither the door nor that operation constrains the field.
Call it
A tools/call carries every argument in one flat object — nothing binds to a path or a query string. This call carries exactly the arguments the operation requires, so it is the smallest one that can run.
curl -X POST https://api.hanzo.ai/v1/mcp \
-H "Authorization: Bearer $HANZO_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "get_v1_agents_sessions_id_control",
"arguments": {
"id": "<id>"
}
}
}'Values are the operation's own defaults and enumerated values where it declares them, and a <placeholder> where neither source declares one. tools/list needs no credential; tools/call does — called without one the door answers HTTP 200 with a JSON-RPC result whose isError is set and whose text says what was missing. How to get a key →
The operation behind it
| Operation | Route | Product | Summary |
|---|---|---|---|
get_v1_agents_sessions_id_control | GET /v1/agents/sessions/{id}/control | agents | Returns the steering commands (pause/resume/stop/message) recorded against the caller's… |
The same capability over plain HTTP is in the agents API reference, on https://api.hanzo.ai.
All 755 tools · The door · API reference
Generated from tools/list on https://api.hanzo.ai/v1/mcp — 833 tools captured 2026-08-01, of which 755 are documented here (the operator surface is not published) (this build read the vendored copy; the door was unreachable).
How is this guide?
get_v1_agents_sessions_id
GetSession returns one session with its direct child sessions and its 50 most recent events, oldest of those first.
get_v1_agents_sessions_id_tree
SessionTree returns the subagent-flow graph rooted at this session: the session, its children, their children, each node carrying its own event count.