Skip to content

Support scoped / read-only personal auth tokens #522

Description

@aki77

Problem
A BugSnag personal auth token (BUGSNAG_AUTH_TOKEN) inherits the full permissions of the user who created it — there is no per-token scope.
For MCP, CI, and other integrations that only need to read error data, this forces the use of a token that can also modify production data: update/delete errors, create/delete projects, regenerate project API keys, and (for admins) invite/remove collaborators. If such a token leaks, the blast radius is the user's entire role across the org.

BUGSNAG_PROJECT_API_KEY only scopes the conversation/operations, not the token's permissions, so it is not a security boundary.

Request
Allow personal auth tokens to be issued with a limited scope, independent of the user's org role — at minimum a read-only scope, ideally fine-grained (e.g. read errors/events vs. write error state vs. admin). This mirrors GitHub fine-grained PATs and GitLab's api_read_only scope.

Benefit
Lets MCP and other automation follow least privilege and limits the damage if a token leaks, without provisioning a dedicated low-privilege seat.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions