VS Code MCP: Reset Trust after you grant Sume the Write scope

Granting Write on Sume's consent page changes what the server can do, but it does not change VS Code's own trust decision for that server. The VS Code page describes trust prompts for MCP servers and a command called MCP: Reset Trust that clears them. Use it when you want VS Code to ask again before running a server whose abilities have changed, and then check the new scopes with mcp_health.

Two separate decisions

The first decision belongs to VS Code and the second to Sume. Granting one does not grant the other.

Moving from read-only to Write

Under mcp:read, Sume hides its write tools. If a model tries one by name, it gets insufficient_scope with required_scope mcp:write. To change that, sign in again and tick Write on the consent page. Then reload the tool list and run mcp_health to confirm the scopes.

If you also want VS Code to confirm the change, run MCP: Reset Trust and let it ask. That is a sensible habit when the same entry moves from browsing models to submitting paid jobs.

Going back

To return to read-only, remove the grant by signing in again without Write; a Sume access token lasts one hour, so an old Write token ages out on its own. Paid and write calls need an idempotency_key whichever scope you use, and max_spend_usd bounds a call only when the agent sends it.

• After any scope change, call mcp_health.
• Keep tool confirmation on for paid tools.
• Use a separate VS Code profile or workspace for sessions that need Write.

Why bother with a reset

MCP: Reset Trust is the VS Code control that makes the editor ask about a server again. After a scope change on Sume, using it turns the new ability into an explicit decision in the editor, which is useful when other people use the same VS Code configuration and never saw Sume's consent page.