sentry_list_issue_events
AI agents call sentry_list_issue_events 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.
The tool is designed to retrieve or query event data from Sentry without modifying state. 'List' operations are characteristic of Read-category tools. However, confidence is moderate (0.75) rather than high because the description is empty and the exact scope of data exposure cannot be fully verified—depending on what 'issue events' includes and access control, it could potentially expose sensitive error logs or…
From the tool's definition Tool name 'sentry_list_issue_events' indicates a listing/retrieval operation ('list') for querying event data from Sentry (error tracking platform). The verb 'list' is a Read operation pattern.
Attacks that exploit this kind of access
sentry_list_issue_events. 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_issue_events: 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_issue_events 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_issue_events 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_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.
sentry_list_issue_events 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 →