bugsnag_set_network_endpoint_groupings

Set the network endpoint grouping rules for a project **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. - endpoints (array) *required*: Array of URL patterns by which network spans are grouped. Endpoints follow OpenAPI path templating syntax (https://swagger.io/specification/#path-templating) where path parameters use curly braces (e.g., /users/{id}). If you encounter colon-prefixed parameters (e.g., :userId from Express/React Router), convert them to curly braces (e.g., {userId}). Wildcards (*) can be used in domains (e.g., https://*.example.com) to match multiple subdomains. **Use Cases:** 1. Consolidate similar API endpoints into single span groups 2. Group dynamic URLs using path parameters (e.g., /api/users/{userId} groups /api/users/123, /api/users/456) 3. Match multiple subdomains using wildcards (e.g., https://*.example.com groups api.example.com, cdn.example.com) 4. Simplify performance monitoring by reducing span group clutter **Examples:** 1. Group API endpoints with path parameters ```json { "endpoints": [ "/api/users/{userId}", "/api/products/{productId}", "/api/orders/{orderId}/items/{itemId}" ] } ``` Expected Output: Success response confirming the update 2. Group endpoints with domain wildcards and path parameters ```json { "endpoints": [ "https://*.example.com/api/v1/{resourceId}", "https://api.example.com/v2/users/{userId}", "/graphql" ] } ``` Expected Output: Success response confirming the update 3. Convert colon-prefixed parameters to curly braces (e.g., from Express/React Router) ```json { "endpoints": [ "/{organizationSlug}/{projectSlug}/performance/view-load", "/api/{version}/items/{itemId}" ] } ``` Expected Output: Success response confirming the update **Hints:** 1. Use Get Network Grouping first to see current patterns 2. Use OpenAPI path templating with curly braces for path parameters: /users/{userId}, /orders/{orderId}/items/{itemId} 3. Convert colon-prefixed parameters to curly braces: :organizationSlug becomes {organizationSlug}, :projectSlug becomes {projectSlug} 4. Wildcards (*) can be used in domains to match subdomains: https://*.example.com/api 5. This replaces all existing patterns - include all patterns you want to keep 6. Well-designed patterns reduce noise in performance monitoring. 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.

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

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

Yes. Add a rate_limit block to the bugsnag_set_network_endpoint_groupings 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.

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