bugsnag_get_events_on_an_error
Gets a list of events that have grouped into the specified error Parameters: - projectId (string): Unique identifier of the project. This is optional if a current project is set and is used to set the current project for BugSnag tools. - errorId (string) *required*: Unique identifier of the error...
This record as markdown: /tools/smartbear-mcp/bugsnag-get-events-on-an-error.md
What bugsnag_get_events_on_an_error does on SmartBear MCP
AI agents call bugsnag_get_events_on_an_error to retrieve information from SmartBear MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
errorId | string | Yes | Unique identifier of the error |
filters | object | — | Apply filters to narrow down the event list. Use the List Project Event Filters tool to discover available filter fields. Time filters support extended ISO 8601 |
nextUrl | string | — | URL for retrieving the next page of results. Use the value in the previous response to get the next page when more results are available. Only values provided i |
perPage | number | — | How many results to return per page. |
direction | string | — | Sort direction for ordering results |
projectId | string | — | Unique identifier of the project. This is optional if a current project is set and is used to set the current project for BugSnag tools. |
Parameters from the server's own tool schema.
Why bugsnag_get_events_on_an_error is rated Low
This is a read-only query tool that retrieves and lists existing event data from BugSnag without any side effects. It performs data retrieval with filtering capabilities, which is characteristic of Read category tools. No data is created, modified, deleted, or executed.
From the tool's definition Tool name includes 'get' and description states 'Gets a list of events' with parameters for querying and filtering. The tool retrieves data about error events with no modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
The rule that runs bugsnag_get_events_on_an_error safely
PolicyLayer is an MCP gateway: it sits between your AI agents and SmartBear MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For bugsnag_get_events_on_an_error, this is the rule to start with:
bugsnag_get_events_on_an_error is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect SmartBear MCP, apply this rule, and every bugsnag_get_events_on_an_error call is checked against it from then on.
Questions about bugsnag_get_events_on_an_error
Gets a list of events that have grouped into the specified error Parameters: - projectId (string): Unique identifier of the project. This is optional if a current project is set and is used to set the current project for BugSnag tools. - errorId (string) *required*: Unique identifier of the error - filters (record<string, array>): Apply filters to narrow down the event list. Use the List Project Event Filters tool to discover available filter fields. Time filters support extended ISO 8601 format (e.g. 2018-05-20T00:00:00Z) or relative format (e.g. 7d, 24h). (default: {"event.since":[{"type":"eq","value":"30d"}],"error.status":[{"type":"eq","value":"open"}]}) - direction (enum): Sort direction for ordering results (default: "desc") - perPage (number): How many results to return per page. (default: 30) - nextUrl (string): URL for retrieving the next page of results. Use the value in the previous response to get the next page when more results are available. Only values provided in the output from this tool can be used. Do not attempt to construct it manually. Use Cases: 1. Retrieving all the events for comparison to find commonalities or differences in stack traces, breadcrumbs and metadata Examples: 1. Get events of an error json { "projectId": "1234567890abcdef12345678", "errorId": "6863e2af012caf1d5c320000" } Expected Output: A list of events, ordered by timestamp, with complete details including stack trace, breadcrumbs, metadata, and context. It is categorised as a Read tool in the SmartBear MCP MCP Server, which means it retrieves data without modifying state.
bugsnag_get_events_on_an_error accepts 6 parameters: errorId, filters, nextUrl, perPage, direction, projectId. Required: errorId. The full parameter table on this page comes from the server's own tool schema.
Register the SmartBear MCP server in PolicyLayer and add a rule for bugsnag_get_events_on_an_error: 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 SmartBear MCP. Nothing to install.
bugsnag_get_events_on_an_error 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 bugsnag_get_events_on_an_error 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 bugsnag_get_events_on_an_error. 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.
bugsnag_get_events_on_an_error is provided by the SmartBear MCP server (SmartBear/smartbear-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on SmartBear, and thousands of servers like it.
This server
Across the catalogue