Expose DSN key rate limits and audit logs in MCP

Open
#1,740 2 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
typescript
Domain
api

Research direction

Start by reading the repository’s MCP tool registrations and the Sentry API client entry points; the issue does not name specific files or tests. Identify the API operations and permissions for reading project DSN key rate limits and audit-log entries, then check how existing MCP tools expose comparable project data. Done means MCP clients can inspect both kinds of data.

Written by the indexing model from the issue text.

Description

3. Medium

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]

Dominant language
TypeScript
Stars
961
Forks
179
Avg merge
15h 33m
Merged PRs (30d)
476

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from getsentry/toolkit

All issues in getsentry/toolkit

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.