Claude Code Elicitation hook block: does Sume ever elicit?

Sume's hosted MCP server is documented as tools-only, so an Elicitation hook has nothing from Sume to decline. Claude Code 2.1.283 (2026-09-25) made a hook returning decision block decline the elicitation, which matters for servers that ask users questions mid-call.

For Sume, the confirmation step lives in tool arguments instead: dry_run, max_spend_usd and idempotency_key.

What changed

Before, a blocking Elicitation hook could be ignored in some paths. Now block declines. A later release, 2.1.287, added support for URL prompts from MCP servers on protocol 2025-11-25.

At a glance

Where Sume asks for confirmation

Sume speaks protocol version 2025-11-25 and exposes tools only; resources, prompts, roots and sampling are unsupported. Confirmation is done by the caller, using a dry run first and a spend ceiling on the real call.

If you want a human in the loop, put the checkpoint in a PreToolUse or permission rule, not in an elicitation.

• No Sume elicitation to hook.
• Use dry_run before paid calls.
• Use permission prompts for write tools.

Limits and what is not verified

I based the tools-only statement on Sume's MCP docs and server source and did not probe for elicitation requests on the wire. Other servers in the same session may still elicit.