Testing the feedback tool sends real feedback

Aberta
  • Algo errado?
#2,264 1 comentário 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
3/5
Tempo estimado
1-2 dias
Facilidade para iniciantes
35/100
Tipo de issue
Funcionalidade
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
typescript
Domínio
api, devtools

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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]

Linguagem predominante
TypeScript
Estrelas
961
Forks
179
Merge médio
15h 33min
PRs com merge (30d)
476

Preparar o ambiente

Este projeto não oferece contêiner de desenvolvimento, Dockerfile nem guia de contribuição, então a configuração fica por sua conta: comece pelo README e veja nosso guia da primeira contribuição para os passos gerais.

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de getsentry/toolkit

Todas as issues de getsentry/toolkit

Issues semelhantes

Mais issues de TypeScript

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.