25 tools from the Sentry MCP Server, categorised by risk level.
View the Sentry policy →analyze_issue_with_seer Use AI to analyse production errors for root cause 2/5 find_dsns List all Sentry DSNs for a project 3/5 find_organizations Find organisations the user has access to 2/5 find_projects Find projects in a Sentry organisation 2/5 find_releases Find releases in a Sentry organisation 2/5 find_teams Find teams in an organisation 2/5 get_doc Fetch markdown content of a Sentry docs page 2/5 get_event_attachment Download attachments from a Sentry event 3/5 get_issue_details Get detailed information about a specific issue 2/5 get_issue_tag_values Get tag value distribution for an issue 2/5 get_sentry_resource Fetch a Sentry resource by URL or type and ID 2/5 get_trace_details Get detailed information about a trace 2/5 list_events Search events using Sentry query syntax 2/5 list_issue_events List events within a specific issue 2/5 list_issues List issues using Sentry query syntax 2/5 search_docs Search Sentry documentation 2/5 search_events Search events with counts and aggregations 2/5 search_issue_events Search and filter events within an issue 2/5 search_issues Search for grouped issues in Sentry 2/5 whoami Identify the authenticated Sentry user 2/5 The Sentry MCP server exposes 25 tools across 2 categories: Read, Write.
Use Intercept, the open-source MCP proxy. Write YAML rules for each tool — rate limits, argument validation, or deny rules — then run Intercept in front of the Sentry server.
Sentry tools are categorised as Read (20), Write (5). Each category has a recommended default policy.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept