search_issues
Search for grouped issues and problems in Sentry
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 search_issues 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 SEARCH_ISSUES
Even though search_issues 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:
search_issues:
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 search_issues tool do?
Search for grouped issues and problems in Sentry. 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 search_issues?
Add a rule in your Intercept YAML policy under the tools section for search_issues. 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 search_issues?
search_issues is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Can I rate-limit search_issues?
Yes. Add a rate_limit block to the search_issues 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 search_issues completely?
Set action: deny in the Intercept policy for search_issues. 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 search_issues?
search_issues 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.