get_sentry_issue
AI agents call get_sentry_issue to retrieve information from Server Puppeteer without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name indicates a data retrieval operation (get_) from Sentry, which is a monitoring/error tracking platform. This aligns with the Read category as it queries and retrieves data without side effects. Severity is medium because unauthorized access to Sentry issues could expose sensitive debugging information, error traces, or credentials.
From the tool's definition Tool name 'get_sentry_issue' suggests retrieval of issue data from Sentry error tracking service; description is empty, limiting specificity.
Attacks that exploit this kind of access
get_sentry_issue. It is categorised as a Read tool in the Server Puppeteer MCP Server, which means it retrieves data without modifying state.
Register the Server Puppeteer MCP server in PolicyLayer and add a rule for get_sentry_issue: 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 Server Puppeteer. Nothing to install.
get_sentry_issue 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 get_sentry_issue 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 get_sentry_issue. 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.
get_sentry_issue is provided by the Server Puppeteer MCP server (@hisma/server-puppeteer). 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 →