bugsnag_list_project_errors

List and search errors in a project using customizable filters and pagination 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. - filters (record<string, array>): Apply filters to narrow down the error 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"}]}) - sort (enum): Field to sort the errors by (default: "last_seen") - 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. Debug recent application errors by filtering for open errors in the last 7 days 2. Generate error reports for stakeholders by filtering specific error types or severity levels 3. Monitor error trends over time using date range filters 4. Find errors affecting specific users or environments using metadata filters Examples: 1. Find errors affecting a specific user in the last 24 hours json { "filters": { "user.email": [ { "type": "eq", "value": "user@example.com" } ], "event.since": [ { "type": "eq", "value": "24h" } ] } } Expected Output: JSON object with a list of errors in the 'data' field, a count of the current page of results in the 'count' field, and a total count of all results in the 'total' field 2. Get the 10 open errors with the most users affected in the last 30 days json { "filters": { "event.since": [ { "type": "eq", "value": "30d" } ], "error.status": [ { "type": "eq", "value": "open" } ] }, "sort": "users", "direction": "desc", "perPage": 10 } Expected Output: JSON object with a list of errors in the 'data' field, a count of the current page of results in the 'count' field, and a total count of all results in the 'total' field 3. Get the next 50 results json { "nextUrl": "https://api.bugsnag.com/projects/515fb9337c1074f6fd000003/errors?base=2025-08-29T13%3A11%3A37Z&direction=desc&filters%5Berror.status%5D%5B%5D%5Btype%5D=eq&filters%5Berror.status%5D%5B%5D%5Bvalue%5D=open&offset=10&per_page=10&sort=users", "perPage": 50 } Expected Output: JSON object with a list of errors, with a URL to the next page if more results are available and a total count of all errors matched Hints: 1. Use List Project Event Filters tool first to discover valid filter field names for your project 2. Combine multiple filters to narrow results - filters are applied with AND logic 3. For time filters: use relative format (7d, 24h) for recent periods or ISO 8601 UTC format (2018-05-20T00:00:00Z) for specific dates 4. Common time filters: event.since (from this time), event.before (until this time) 5. The 'event.since' filter and 'error.status' filters are always applied and if not specified are set to '30d' and 'open' respectively 6. There may not be any errors matching the filters - this is not a problem with the tool, in fact it might be a good thing that the user's application had no errors 7. This tool returns paged results. The 'page_error_count' field indicates the number of results returned in the current page, and the 'total_error_count' field indicates the total number of results across all pages. 8. If the output contains a 'next_url' value, there are more results available - call this tool again supplying the next URL as a parameter to retrieve the next page. 9. Do not modify the next URL as this can cause incorrect results. The only other parameter that can be used with 'next' is 'per_page' to control the page size. It is categorised as a Read tool in the SmartBear MCP MCP Server, which means it retrieves data without modifying state.

bugsnag_list_project_errors accepts 6 parameters: sort, filters, nextUrl, perPage, direction, projectId. 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_list_project_errors: 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_list_project_errors 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_list_project_errors 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_list_project_errors. 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_list_project_errors 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.