Repository navigation
feat(tools): Return DSN status and rate limit from find_dsns - #2102
Open
sentry-junior[bot] wants to merge 3 commits into
Open
sentry-junior[bot] wants to merge 3 commits into
sentry-junior[bot] wants to merge 3 commits into
Conversation
find_dsns only returned the DSN id, name, and public DSN, so there was no way to read a DSN's rate limit through MCP even though update_dsn can set it. The Sentry project keys API already returns isActive and rateLimit; map both into the structured output. rateLimit is null when no limit is set, matching what Sentry returns. Co-Authored-By: Saad Khan <saad.khan@sentry.io>
…imit Co-Authored-By: Saad Khan <saad.khan@sentry.io> # Conflicts: # packages/mcp-core/src/skillDefinitions.json # packages/mcp-core/src/toolDefinitions.json # packages/mcp-core/src/tools/catalog/find-dsns.ts
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 6942246. Configure here.
update_dsn returns rateLimit as { count, windowSeconds }. Use the same
field names in find_dsns so agents see one shape across both tools.
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
You can set a DSN's rate limit through MCP with
update_dsn, but there was no way to read it back.find_dsnsonly returnedid,name, anddsn, even though the project keys endpoint already returnsisActiveandrateLimit.This adds both fields to
find_dsns's structured output:isActive: whether the DSN is enabledrateLimit:{ count, windowSeconds }, the same shapeupdate_dsnreturns, ornullwhen no limit is set. Sentry'sProjectKeySerializeralready returnsnullwhen either value is unset, so this passes that through.The fields are mapped explicitly instead of spreading the passthrough API object, so backend-only fields like the secret DSN still can't leak. The existing test covers both a rate-limited DSN and an unlimited one.
via Saad Khan.
--
View Session [Sentry]