bugsnag_update_error

// WHEN AI AGENTS USE THIS TOOL

AI agents use bugsnag_update_error to create or modify resources in SmartBear MCP. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

// WHY ENFORCE A POLICY ON BUGSNAG_UPDATE_ERROR

Without a policy, an AI agent could call bugsnag_update_error repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach SmartBear MCP.

// RECOMMENDED POLICY

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

smartbear-mcp.yaml

tools:
  bugsnag_update_error:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full SmartBear MCP policy for all 147 tools.

// DETAILS

Tool Name bugsnag_update_error

Category Write

MCP Server SmartBear MCP MCP Server

Risk Level Medium

// MORE SMARTBEAR MCP TOOLS

Destructive collaborator_delete_collaborator_remote_system_configuration Destructive reflect_cancel_suite_execution Destructive reflect_delete_previous_step Destructive swagger_delete_portal_product Destructive swagger_delete_table_of_contents Execute collaborator_reviewservice_action Execute contract-testing_can_i_deploy Execute qmetry_link_issues_to_testcase_run

View all 147 tools →

// RELATED READING

// FAQ

What does the bugsnag_update_error tool do? +

Update the status of an 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 - operation (enum) *required*: The operation to apply to the error - issue_url (string): The URL of the issue to link to the error - required when operation is 'link_issue' - reopenRules (object): Reopen rules for snooze operation - required when operation is 'snooze' **Use Cases:** 1. Mark an error as open, fixed or ignored 2. Discard or un-discard an error 3. Update the severity of an error 4. Snooze an error with defined conditions for when it should be reopened **Examples:** 1. Mark an error as fixed ```json { "errorId": "6863e2af8c857c0a5023b411", "operation": "fix" } ``` Expected Output: Success response indicating the error was marked as fixed 2. Snooze an error for 1 hour ```json { "errorId": "6863e2af8c857c0a5023b411", "operation": "snooze", "reopenRules": { "reopenIf": "occurs_after", "seconds": 3600 } } ``` Expected Output: Success response indicating the error was snoozed for 1 hour 3. Snooze an error until 5 additional users are affected ```json { "errorId": "6863e2af8c857c0a5023b411", "operation": "snooze", "reopenRules": { "reopenIf": "n_additional_users", "additionalUsers": 5 } } ``` Expected Output: Success response indicating the error was snoozed until 5 additional users are affected 4. Snooze an error until 10 occurrences in 24 hours ```json { "errorId": "6863e2af8c857c0a5023b411", "operation": "snooze", "reopenRules": { "reopenIf": "n_occurrences_in_m_hours", "occurrences": 10, "hours": 24 } } ``` Expected Output: Success response indicating the error was snoozed until 10 occurrences in 24 hours 5. Link a Jira issue to an error ```json { "errorId": "6863e2af8c857c0a5023b411", "operation": "link_issue", "issue_url": "https://smartbear.atlassian.net/browse/PIPE-9547" } ``` Expected Output: Success response indicating the Jira issue was linked to the error 6. Unlink a Jira issue from an error ```json { "errorId": "6863e2af8c857c0a5023b411", "operation": "unlink_issue" } ``` Expected Output: Success response indicating the Jira issue was unlinked from the error **Hints:** 1. Only use valid operations - BugSnag may reject invalid values 2. When using 'snooze' operation, reopenRules parameter is required 3. When using 'link_issue' operation, issue_url parameter is required 4. Use 'unlink_issue' to remove the link between an error and its issue 5. For 'occurs_after' reopen rules, specify 'seconds' parameter 6. For 'n_additional_users' reopen rules, specify 'additionalUsers' parameter (max 100,000) 7. For 'n_occurrences_in_m_hours' reopen rules, specify both 'occurrences' and 'hours' parameters 8. For 'n_additional_occurrences' reopen rules, specify 'additionalOccurrences' parameter 9. Snoozing temporarily silences an error until the specified reopen condition is met. It is categorised as a Write tool in the SmartBear MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on bugsnag_update_error? +

Add a rule in your Intercept YAML policy under the tools section for bugsnag_update_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_update_error? +

bugsnag_update_error is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit bugsnag_update_error? +

Yes. Add a rate_limit block to the bugsnag_update_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_update_error completely? +

Set action: deny in the Intercept policy for bugsnag_update_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_update_error? +

bugsnag_update_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.

Enforce policies on SmartBear MCP