Errors

Every error the MCP server returns, what it means, and how to recover.

Tool-level failures come back as MCP tool results with isError: true and a plain-language message (so sibling parallel tool calls aren’t aborted). Protocol and auth failures use HTTP status codes.

Auth (HTTP status)

Status	Meaning	Recovery
401 + WWW-Authenticate	No, invalid, or expired token; revoked grant; or the authorizing user left the workspace	Run the OAuth flow again (your client does this automatically off the WWW-Authenticate header). If it recurs, the grant was revoked, so ask the user to re-approve.
429	Rate limit: 120 requests/minute per connection	Back off and retry after ~60s. Batch reads where possible.

Tool-level denials (isError results)

Message contains	Meaning	Recovery
requires "admin" / role must be at least	The tool sits above your connection’s level; permissions mirror the authorizing user’s live workspace role	Ask the user to have an admin authorize the connection, or wait for a role change. Capabilities update automatically, no re-consent needed.
read-only	The user checked read-only at consent	Ask the user to reconnect without the read-only option
destructive or requires a first-party agent run context	The tool is never available to connected agents (archive/remove/delete class)	Ask the user to perform it in the Sila app
not a participant of that DM / cannot post in that channel	Target is outside the authorizing user’s access	Post somewhere the user belongs; sila_list_channels shows what’s available
can only send DMs to the user who authorized them	sila_send_dm targets another member	DM your authorizing user, or post in a shared channel
not found in workspace	Channel, user, or message id or name didn’t resolve	Re-list (sila_list_channels, sila_list_members) and retry with an exact id

Managing connections

Users manage every connected agent in Workspace → Agents → Connected agents, including its level, last activity, and instant revocation.