Sume tool missing in Claude Code: org block or read-only scope?

A Sume tool can be missing from Claude Code for two different reasons, and the 2.1.283 /mcp list now separates one of them. Tools your organization blocked appear with a warning icon. A tool hidden because the OAuth session has only mcp:read does not appear at all, because Sume does not list mutating or paid tools to a read-only session.

The warning icon is from the Claude Code changelog entry dated September 25, 2026, read 2026-10-01. The scope behavior is from Sume's OAuth and API keys page.

What does the warning icon mean?

The changelog says the /mcp tool list shows more tools at once, scrolls with the page keys and mouse, and marks tools your organization blocked with a warning icon. The block comes from your organization's policy in Claude Code, not from Sume. If you see the icon, ask whoever manages your Claude Code settings.

Why would a Sume tool not be listed at all?

Under OAuth, the default grant is mcp:read. Per the docs, a read-only session sees read-only tools, and generate_image, generate_video or avatars_create appear only when Write was turned on at consent, or when you use an API key. Sume also leaves two legacy caption tools out of tools_list, though they stay callable by name.

How do I check what Sume exposes to my session?

Ask the agent to call tools_list, which lists every tool visible to the current session with safety metadata, and tools_schema with a name for one tool's contract. catalog_list is broader: it lists public API capabilities, some of which have no MCP tool. The tools and gates page covers all three.

How do I get write tools without an API key?

Run the sign-in again and turn the Write toggle on at the consent page on the MCP host; there is no mcp:paid scope, so Write is the only extra grant. Claude Code then lists the mutating and paid tools. Keep idempotency_key on every paid submit.