Claude Always allow for read-only MCP tools: Sume's tools

Claude Desktop v2.110.0 and v1.46388.0 now offer an Always allow choice for read-only tools from managed and built-in MCP servers, unless an admin sets mcpPersistentAlwaysAllowEnabled to false. On Sume, only tools marked read-only can ever reach that choice.

Sume's read tools set readOnlyHint true, idempotentHint true, destructiveHint false and openWorldHint false. Its write tools set readOnlyHint false, so they keep prompting.

What the setting changes

Before, a user might approve the same lookup repeatedly. Now the prompt can include a persistent allow for the read-only ones. An admin who does not want persistent decisions turns the flag off.

At a glance

What counts as read-only on Sume

The classification comes from the tool annotations the server sends, not from the tool name. Sume's discovery and listing tools are read tools. Anything that mutates or spends is a write tool, needs the mcp:write scope, and requires an idempotency_key.

That makes Always allow low-risk for tools_list and similar calls, while a paid create still asks.

• Set mcpPersistentAlwaysAllowEnabled to false for strict review environments.
• Leave it on if you want fewer prompts for lookups.
• Never rely on Always allow for spend control; use max_spend_usd and spend caps.

Limits and what is not verified

The changelog does not say how Claude treats a tool with no annotations, and I did not test the prompt flow against Sume. The annotation values come from Sume's server source, and the offer rule comes from the changelog.