bugsnag_update_error

SERVERSmartBear MCP SOURCESmartBear/smartbear-mcp

Medium RISK CLASS

Category Write

Parameters 52 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/smartbear-mcp/bugsnag-update-error.md

WHAT IT DOES

What bugsnag_update_error does on SmartBear MCP

AI agents use bugsnag_update_error to create or update resources in SmartBear MCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your SmartBear MCP environment.

Parameter	Type	Required	Description
`errorId`	string	Yes	Unique identifier of the error
`issue_url`	string	—	The URL of the issue to link to the error - required when operation is 'link_issue'
`operation`	string	Yes	The operation to apply to the error
`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.
`reopenRules`	object	—	Reopen rules for snooze operation - required when operation is 'snooze'

Parameters from the server's own tool schema.

RISK

Why bugsnag_update_error is rated Medium

This tool modifies error status and metadata (link_issue, snooze operations) but does not permanently delete data or execute arbitrary code. The operations are state transitions that can be reversed (e.g., reopening a fixed error, unlinking an issue). This fits the Write category.

From the tool's definition Tool description states 'Update the status of an error' with operations including marking errors as 'open, fixed or ignored' and ability to 'link_issue' or 'snooze'. These are reversible state modifications that change error metadata without deletion.

Risk signalsHigh parameter count (11 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs bugsnag_update_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_update_error, this is the rule to start with:

bugsnag_update_error Rate-limited

bugsnag_update_error stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "bugsnag_update_error": {
      "limits": [
        {
          "counter": "bugsnag_update_error_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect SmartBear MCP, apply this rule, and every bugsnag_update_error call is checked against it from then on.

FAQ

Questions about bugsnag_update_error

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.

What parameters does bugsnag_update_error accept? +

bugsnag_update_error accepts 5 parameters: errorId, issue_url, operation, projectId, reopenRules. Required: errorId, operation. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on bugsnag_update_error? +

Register the SmartBear MCP server in PolicyLayer and add a rule for bugsnag_update_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.

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

How do I block bugsnag_update_error completely? +

Set action: deny in the PolicyLayer 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 server (SmartBear/smartbear-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on SmartBear, and thousands of servers like it.

This server

All 240 SmartBear tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP →team_manager_update_budget on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →