Get recent error events (level:error, limit 10). Use for real-time error detection after deploys. Structured data, no screenshot parsing needed (~500 tokens saved).
AI agents call sentry_events to retrieve information from Perceptdot without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns error event data from Sentry without creating, modifying, deleting, or executing operations. It is purely informational/diagnostic in nature. The fixed limit (10 events) and structured response format confirm it is a read-only retrieval operation with minimal blast radius if misused—an agent would only gain visibility into recent errors, not cause damage.
From the tool's definition Tool retrieves 'recent error events' with a fixed limit and specified filters (level:error, limit 10). The description explicitly states 'Use for real-time error detection' and mentions 'Structured data', indicating data retrieval without modification or side…
Attacks that exploit this kind of access
Get recent error events (level:error, limit 10). Use for real-time error detection after deploys. Structured data, no screenshot parsing needed (~500 tokens saved). It is categorised as a Read tool in the Perceptdot MCP Server, which means it retrieves data without modifying state.
Register the Perceptdot MCP server in PolicyLayer and add a rule for sentry_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 Perceptdot. Nothing to install.
sentry_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_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_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_events is provided by the Perceptdot MCP server (perceptdot/percept). 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 →