Testing the feedback tool sends real feedback

Offen
  • Stimmt etwas nicht?
#2,264 1 Kommentar 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
3/5
Geschätzter Aufwand
1-2 Tage
Anfängerfreundlichkeit
35/100
Issue-Typ
Feature
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
typescript
Bereich
api, devtools

Rechercherichtung

Start with the tool definition in packages/mcp-core/src/tools/catalog/submit-feedback-to-sentry-team.ts, especially the hints around line 73 and the input schema around lines 78-109. Then check packages/mcp-core/src/server.ts near line 405, where the outputSchema is published, and availability.ts lines 123-127, which hide the tool without a DSN. Done means a dry-run input that validates and returns the same response shape without capturing feedback, with the design for the DSN-less case settled first.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

submit_feedback_to_sentry_team has no way to be exercised without capturing a real User Feedback in mcp-server. Its hints say not to call it for testing (packages/mcp-core/src/tools/catalog/submit-feedback-to-sentry-team.ts:73), but clients that verify the tool or record tool response shapes call it anyway, and every call lands in the feedback inbox.

  • MCP-SERVER-GQ6 (2026-11-14 05:15 UTC): an other-family client (python-httpx) asked for a dry-run flag because "building a faithful client or replica means sending real feedback."
  • The same caller (matched by client IP; no mcp.session.id or user.id was recorded) called ~100 tools between 05:10 and 05:15 UTC while documenting response shapes, including writes like create_team, create_project and update_dsn. It called submit_feedback_to_sentry_team three times in five seconds: one probe rejected for an oversized toolName, then MCP-SERVER-GQ7 (asks to document the result text) and MCP-SERVER-GQ6. Both returned {"feedbackId": ...}.
  • Other test or meta submissions in the last 30 days: MCP-SERVER-GH9 and MCP-SERVER-GHA (2026-10-30, a maintainer checking end-to-end delivery through the hosted connector), MCP-SERVER-GP8 (2026-11-12, feedback about the feedback tool).
  • The tool has no dryRun input (submit-feedback-to-sentry-team.ts:78-109), and no MCP tool in mcp-core has one. Its result shape is already published as outputSchema in tools/list (packages/mcp-core/src/server.ts:405). Locally it can't be used as a sandbox either: it's hidden when Sentry telemetry has no DSN (packages/mcp-core/src/tools/catalog-runtime/availability.ts:123-127).

Proposal from the reporter of MCP-SERVER-GQ6: add a dry-run flag that validates input and returns the response shape without capturing feedback.

via Sentry.

--

View Session [Sentry]

Vorherrschende Sprache
TypeScript
Sterne
961
Forks
179
Ø Merge
15 Std. 33 Min.
Gemergte PRs (30 T.)
476

Entwicklungsumgebung

Dieses Projekt bietet weder Dev-Container noch Dockerfile noch Beitragsleitfaden – die Einrichtung liegt bei Ihnen. Beginnen Sie mit der README; die allgemeinen Schritte stehen in unserem Leitfaden für den ersten Beitrag.

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus getsentry/toolkit

Alle Issues in getsentry/toolkit

Ähnliche Issues

Weitere Issues zu TypeScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.