{
  "data": null,
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/niches/agent-auth.refused-scope/",
    "json": "https://www.anchorterminal.com/niches/agent-auth.refused-scope/index.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/niches/agent-auth.refused-scope/index.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/niches/agent-auth.refused-scope/index.min.md"
  },
  "markdown": "No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.\n\n| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |\n| --- | --- | --- | --- | --- |\n| 0 | 14 | 15 | 9 | 4 |\n\n## What counts as done\n\nThe 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.\n\nHow agents ask for it: why can't the agent see my calendar; which permissions did I grant; reconnect with write access\n\n## Does the job, with a limit\n\nIt 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.\n\n- **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.\n- **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.\n- **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.\n- **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.\n- **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.\n- **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.\n- **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.\n- **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.\n- **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.\n- **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.\n- **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.\n- **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.\n- **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.\n- **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.\n\n## What stops agents finishing\n\n- errors swallowed inside the SDK\n- rejection happens in the user's browser after redirect, invisible to the service\n- write scopes requested on every connection with no read-only option (Clerk MCP)\n\n## Around it\n\nBefore: agent-auth.connect-user-account. After: agent-auth.out-of-band-consent.\n\n## Where this comes from\n\nWeight 9 of 100 in Agent auth \u0026 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\n\nAs 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.\n",
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "attributionRequired": true,
    "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-11-16",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "0.8",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run",
    "terms": "https://www.anchorterminal.com/terms/#data"
  },
  "page": {
    "breadcrumbs": [
      {
        "name": "Home",
        "url": "https://www.anchorterminal.com/"
      },
      {
        "name": "For agents",
        "url": "https://www.anchorterminal.com/agents/"
      },
      {
        "name": "Niches",
        "url": "https://www.anchorterminal.com/niches/"
      },
      {
        "name": "Find out a scope was refused or a connection is missing, and recover",
        "url": ""
      }
    ],
    "description": "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 \u0026 delegated access with the reason and a source.",
    "facts": null,
    "h1": "Find out a scope was refused or a connection is missing, and recover",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/niches/agent-auth.refused-scope/",
    "published": "",
    "section": "agents",
    "title": "Find out a scope was refused or a connection is missing, and recover…",
    "toc": null,
    "updated": "2026-11-15",
    "url": "https://www.anchorterminal.com/niches/agent-auth.refused-scope/"
  },
  "tokens": {
    "markdown": 1500,
    "slim": 380
  },
  "version": 1
}
