list_issue_events
List events within a specific issue
Part of the Sentry MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
WHEN AI AGENTS USE THIS TOOL
AI agents call list_issue_events to retrieve information from Sentry without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions — but you may still want rate limits to control API costs.
WHY ENFORCE A POLICY ON LIST_ISSUE_EVENTS
Even though list_issue_events only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
RECOMMENDED POLICY
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
tools:
list_issue_events:
rules:
- action: allowSee the full Sentry policy for all 25 tools.
DETAILS
MORE SENTRY TOOLS
find_dsns Read find_organizations Read find_projects Read find_releases Read find_teams Read get_doc Read get_event_attachment Read get_issue_details Read SIMILAR READ TOOLS ON OTHER SERVERS
list_bases Airtable list_tables Airtable list_records Airtable get_record Airtable search_records Airtable search Amplitude RELATED READING
FREQUENTLY ASKED QUESTIONS
What does the list_issue_events tool do?
List events within a specific issue. It is categorised as a Read tool in the Sentry MCP Server, which means it retrieves data without modifying state.
How do I enforce a policy on list_issue_events?
Add a rule in your Intercept YAML policy under the tools section for list_issue_events. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Sentry MCP server.
What risk level is list_issue_events?
list_issue_events is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Can I rate-limit list_issue_events?
Yes. Add a rate_limit block to the list_issue_events rule in your Intercept policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
How do I block list_issue_events completely?
Set action: deny in the Intercept policy for list_issue_events. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
What MCP server provides list_issue_events?
list_issue_events is provided by the Sentry MCP server (getsentry/sentry-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
ENFORCE POLICIES ON SENTRY
Open source. One binary. Zero dependencies.