---
schema: 1
type: term
title: _OAuth scopes_
description: >-
  **_OAuth scopes_** are granular permission labels in the OAuth authorization
  framework that define exactly which actions an application — here, an AI agent
  — is allowed to perform with an API. In this material, enforcing security
  through proper scopes at the **API layer itself** is presented as the right
  way to limit what agents can do, rather than restricting what the MCP layer
  exposes.
canonical: 'https://liquidgold.cc/channel/everyinc/explore/term/oauth-scopes-1ed6cdce5eea'
markdown: >-
  https://liquidgold.cc/channel/everyinc/explore/term/oauth-scopes-1ed6cdce5eea.md
llms: null
parent: 'https://liquidgold.cc/channel/everyinc/llms.txt'
channel: everyinc
updated: '2026-10-23T22:12:35.346Z'
language: null
children: []
---


# \_OAuth scopes\_

Canonical: https://liquidgold.cc/channel/everyinc/explore/term/oauth-scopes-1ed6cdce5eea

Parent: [Channel index](https://liquidgold.cc/channel/everyinc/llms.txt)

## Definition

**_OAuth scopes_** are granular permission labels in the OAuth authorization framework that define exactly which actions an application — here, an AI agent — is allowed to perform with an API. In this material, enforcing security through proper scopes at the **API layer itself** is presented as the right way to limit what agents can do, rather than restricting what the MCP layer exposes.

<Section title="Where OAuth scopes show up in the material">## How **_OAuth scopes_** are used hereIn this channel's material, **OAuth scopes** appear in the context of **agent security**. Alex Rattray argues that limiting what an **MCP server** exposes is the wrong security lever, because anything in the underlying API remains reachable under the hood — so security has to be enforced at the **API layer itself**, using OAuth with granular permissions and proper scopes.### Why scopes, not the MCP layer- The MCP layer is just a translation surface; the real authority over what an agent can do lives with the **API provider**.- **Granular permissions** mean an agent can be granted narrow rights — read, refund, create — rather than blanket access.- The API layer can verify and enforce those rights on every request, no matter which client or tool surface is calling.<MomentLink seconds="2454"/>[^913c216d-5ccb-51d9-8f42-8feb7c017d9d@2454]### The broader security pictureThe same interview pairs scopes with another defense: **one API provider per sandbox**, locking network access so nothing can connect out except the target API — `api.stripe.com` and nothing else. Together, OAuth scopes at the API layer and network-locked sandboxes form the security model for agents that write and execute code.### Key takeawayScopes are the concrete mechanism by which an agent gets _least-privilege_ access to an API — decided at the API layer, not at the protocol or tool layer.</Section>