You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Expose DSN key rate limits and audit logs in MCP #1740
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.
Activity
linear-code commentedon Oct 29, 2026
MCP-1132
sentry-junior commentedon Nov 9, 2026
Current state of the two parts of this issue:
DSN rate limits.
update_dsncan set a key's rate limit, butfind_dsnsdrops it from its output even though the project keys API returns it. #2102 is one possible fix: it addsisActiveandrateLimit({ count, windowSeconds }, the same shape asupdate_dsn) tofind_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/, butOrganizationAuditPermissionrequiresorg:writeforGET, notorg:read. So any tool here would only work for connections that already have that scope. #2102 doesn't touch this part.