sentry_list_issues

What sentry_list_issues does on Integrations MCP

AI agents call sentry_list_issues to retrieve information from Integrations MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why sentry_list_issues is rated Low

List operations are inherently Read category—they query and retrieve data without side effects. The absence of description lowers confidence slightly, but the name provides sufficient clarity that this fetches existing issues rather than creating, modifying, or deleting them. Blast radius is low since reading error tracking data poses minimal security risk in isolation.

From the tool's definition Tool name 'sentry_list_issues' indicates a list operation, which is a read-only query. The verb 'list' retrieves data without modifying or deleting it. Sentry is an error tracking platform, so listing issues retrieves historical error/event data.

The rule that runs sentry_list_issues safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Integrations MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For sentry_list_issues, this is the rule to start with:

{
  "version": "1",
  "default": "deny",
  "tools": {
    "sentry_list_issues": {}
  }
}

Questions about sentry_list_issues