Skip to content

Expose DSN key rate limits and audit logs in MCP #1740

Open

Description

@sentry-junior

Add MCP support for:

  • Reading rate limits configured on a project's DSN keys.
  • Accessing Sentry audit-log entries.

This would let MCP clients inspect project key limits and audit activity directly.

via Ido Shemesh.

--

View Junior Session [Sentry]

Activity

  1. linear-code commented on Oct 29, 2026

    @linear-code
  2. sentry-junior commented on Nov 9, 2026

    @sentry-junior
    ContributorAuthor

    Current state of the two parts of this issue:

    DSN rate limits. update_dsn can set a key's rate limit, but find_dsns drops it from its output even though the project keys API returns it. #2102 is one possible fix: it adds isActive and rateLimit ({ count, windowSeconds }, the same shape as update_dsn) to find_dsns. It's a proposal, not the required approach.

    Audit logs. No MCP tool reads audit-log entries yet. Sentry exposes GET /api/0/organizations/{org}/audit-logs/, but OrganizationAuditPermission requires org:write for GET, not org:read. So any tool here would only work for connections that already have that scope. #2102 doesn't touch this part.

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

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions