Testing the feedback tool sends real feedback

Open
  • Is something wrong?
#2,264 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
typescript
Domain
api, devtools

Research direction

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.

Written by the indexing model from the issue text.

Description

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]

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.