# Find out a scope was refused or a connection is missing, and recover

> Find out a scope was refused or a connection is missing, and recover: 0 companies fully do it, 14 with a limit, 15 carry the tag. Every listing in Agent auth & delegated access with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/agent-auth.refused-scope/
- Markdown: https://www.anchorterminal.com/niches/agent-auth.refused-scope/index.md (~1,500 tokens)
- Slim: https://www.anchorterminal.com/niches/agent-auth.refused-scope/index.min.md (~380 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/agent-auth.refused-scope/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 0 | 14 | 15 | 9 | 4 |

## What counts as done

The call that needs the missing scope returns a typed error naming the scope or the connection state and a reconnect URL, never a silent empty result or a swallowed exception, and the agent stops retrying after one such answer.

How agents ask for it: why can't the agent see my calendar; which permissions did I grant; reconnect with write access

## Does the job, with a limit

It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.

- **Aembit (Aembit, Inc.)**: Consent failures come back to redirect_uri as access_denied with a named description, including declined consent. No per-call error naming a missing scope with a reconnect URL is documented.
- **Amazon Bedrock AgentCore Identity (Amazon Web Services, Inc.)**: Gateway answers 403 with error="insufficient_scope" and the scope for inbound calls. For outbound grants no typed refused-scope error is documented; the advice is to retry with forceAuthentication on a 401.
- **Arcade.dev (Arcade AI, Inc.)**: Authorization responses name the scopes and status, and a tool run that needed authorization is recorded as such. The docs show checking with authorize before execute; a typed missing-scope error from execute itself is not shown.
- **Auth0 for AI Agents (Token Vault) (Okta, Inc.)**: The exchange returns granted scopes and a 401 when no connected account is found. Auth0 AI SDK issue 175, still open, reports Token Vault exchange errors swallowed inside the SDK, which this use case names as a blocker.
- **Clerk MCP server (Clerk, Inc.)**: whoami shows granted permissions and a tool returns a permission error when a scope or role is missing, but the fix is to sign out and reconnect, no reconnect URL is returned, and every connection asks for write scopes with no read-only set.
- **Cloudflare Workers OAuth Provider (Cloudflare, Inc.)**: Resource servers can answer 403 insufficient_scope naming every required scope, and 401 challenges point at the metadata. The handler must call insufficientScope itself, since requiredScopes is advertised, not enforced.
- **Descope Agentic Identity Hub (Descope, Inc.)**: Users may decline a scope when the MCP server allows it, and an unlinked account raises ConnectionAuthorizationRequired with a connect URL. No error naming a specific missing scope is documented; a tenant mismatch returns a plain 404 Token not found.
- **Keycard (Keycard Labs, Inc.)**: The token endpoint returns insufficient_authorization for a missing or revoked grant and access_denied for a policy refusal, and denials are readable in the Console. The SDK never throws, so an agent sees the error only if the server checks AccessContext.
- **Microsoft Entra Agent ID (Microsoft Corporation)**: Entra returns named AADSTS errors, such as 82014 for interactive consent on an agent and 50013 for a wrong-audience assertion. No agent-specific missing-scope error with a reconnect URL is documented.
- **Nango (Nango Inc)**: A 403 such as a missing scope fails that tool only, and a 401 tells the agent the connection needs reconnecting; the reconnect link requests current scopes. The link comes from a separate meta-tool that is off by default, not in the error itself.
- **Scalekit AgentKit (ScaleKit, Inc.)**: Users can clear optional scopes, and tool calls needing them fail with the app's own permission error, a 403 passed through. No Scalekit error names the missing scope or returns a reconnect link.
- **Stytch Connected Apps (Twilio Inc.)**: The consent page refuses scopes the user's roles cannot grant, and MCP servers answer 401 with resource metadata. No error naming a missing scope for a later call is documented; enforcement is left to the resource server.
- **Vercel Connect (Vercel Inc.)**: Auth failures are typed: UserAuthorizationRequiredError, ConnectorInstallationRequiredError, NoValidTokenError and 403s naming the missing project link. No error that names a refused provider scope is documented.
- **WorkOS Pipes and Agents (WorkOS, Inc.)**: The token response lists granted scopes and missing_scopes and a typed needs_reauthorization error, so a refused scope is visible. The reconnect URL is not in that response; it needs a get-authorize-url call.

## What stops agents finishing

- errors swallowed inside the SDK
- rejection happens in the user's browser after redirect, invisible to the service
- write scopes requested on every connection with no read-only option (Clerk MCP)

## Around it

Before: agent-auth.connect-user-account. After: agent-auth.out-of-band-consent.

## Where this comes from

Weight 9 of 100 in Agent auth & delegated access: 4 of 33 accounts (Auth0 swallowed errors, Arcade auth error, Nango CIMD dead end, Linear invalid client); buyer check 2 asks for it

As data: https://www.anchorterminal.com/api/v1/use-cases/agent-auth.refused-scope.json, or the MCP tool get_use_case with id agent-auth.refused-scope. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
