Testing the feedback tool sends real feedback

Aperta
  • Qualcosa non va?
#2,264 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
35/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
typescript
Ambito
api, devtools

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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]

Lingua principale
TypeScript
Stelle
961
Fork
179
Merge medio
15h 33m
PR unite (30g)
476

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di getsentry/toolkit

Tutte le issue di getsentry/toolkit

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.