bugsnag_get_events_on_an_error

// WHEN AI AGENTS USE THIS TOOL

AI agents call bugsnag_get_events_on_an_error to retrieve information from SmartBear MCP without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

// WHY ENFORCE A POLICY ON BUGSNAG_GET_EVENTS_ON_AN_ERROR

Even though bugsnag_get_events_on_an_error only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

// RECOMMENDED POLICY

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

smartbear-mcp.yaml

tools:
  bugsnag_get_events_on_an_error:
    rules:
      - action: allow

See the full SmartBear MCP policy for all 243 tools.

// DETAILS

Tool Name bugsnag_get_events_on_an_error

Category Read

MCP Server SmartBear MCP MCP Server

Risk Level Low

// MORE SMARTBEAR MCP TOOLS

Destructive collaborator_delete_collaborator_remote_system_configuration Destructive contract-testing_admin_delete_role Destructive contract-testing_admin_delete_team Destructive contract-testing_admin_delete_user Destructive contract-testing_admin_remove_role_from_user Destructive contract-testing_admin_remove_user_from_team Destructive contract-testing_admin_reset_roles Destructive contract-testing_delete_all_integrations

View all 243 tools →

// WHAT CAN GO WRONG

Agents calling read-class tools like bugsnag_get_events_on_an_error have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

// OTHER READ TOOLS ACROSS MCP SERVERS

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

Firecrawl Web Scraping Server firecrawl_check_crawl_status Firecrawl Web Scraping Server firecrawl_crawl Firecrawl Web Scraping Server firecrawl_deep_research Firecrawl Web Scraping Server firecrawl_extract Firecrawl Web Scraping Server firecrawl_map Firecrawl Web Scraping Server firecrawl_scrape

// RELATED READING

// FAQ

What does the bugsnag_get_events_on_an_error tool do? +

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.

How do I enforce a policy on bugsnag_get_events_on_an_error? +

Add a rule in your Intercept YAML policy under the tools section for bugsnag_get_events_on_an_error. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the SmartBear MCP MCP server.

What risk level is bugsnag_get_events_on_an_error? +

bugsnag_get_events_on_an_error is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit bugsnag_get_events_on_an_error? +

Yes. Add a rate_limit block to the bugsnag_get_events_on_an_error rule in your Intercept 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.

How do I block bugsnag_get_events_on_an_error completely? +

Set action: deny in the Intercept 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.

What MCP server provides bugsnag_get_events_on_an_error? +

bugsnag_get_events_on_an_error is provided by the SmartBear MCP MCP server (@smartbear/mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Let agents act without letting them run wild.