sentry_list_issues
AI agents call sentry_list_issues to retrieve information from Integrations MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
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.
Attacks that exploit this kind of access
sentry_list_issues. It is categorised as a Read tool in the Integrations MCP MCP Server, which means it retrieves data without modifying state.
Register the Integrations MCP server in PolicyLayer and add a rule for sentry_list_issues: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Integrations MCP. Nothing to install.
sentry_list_issues is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the sentry_list_issues rule in your PolicyLayer 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.
Set action: deny in the PolicyLayer policy for sentry_list_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.
sentry_list_issues is provided by the Integrations MCP server (shriram-vasudevan/integrations-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →