bugsnag_list_spans
Get individual spans belonging to a span group 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. - spanGroupId (string) *required*: ID of the span group - sort (enum): Field to...
This record as markdown: /tools/smartbear-mcp/bugsnag-list-spans.md
What bugsnag_list_spans does on SmartBear MCP
AI agents call bugsnag_list_spans to retrieve information from SmartBear MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
sort | string | — | Field to sort by |
filters | object | — | Apply filters to narrow down the span group list. Use the List Trace Fields tool to discover available filter fields. Time filters support extended ISO 8601 for |
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 i |
perPage | number | — | How many results to return per page. |
direction | string | — | Sort direction for ordering results |
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. |
spanGroupId | string | Yes | ID of the span group |
Parameters from the server's own tool schema.
Why bugsnag_list_spans is rated Low
This tool retrieves and queries spans data from BugSnag's error tracking system with no side effects. It supports read-only operations like listing, filtering, and pagination. There is no capability to create, modify, delete, or execute actions—only to fetch and display existing span data.
From the tool's definition Tool name 'bugsnag_list_spans' and description 'Get individual spans belonging to a span group' indicate data retrieval. Parameters include sorting, pagination (perPage, nextUrl), and filtering options typical of query operations.
Attacks that exploit this kind of access
The rule that runs bugsnag_list_spans 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_list_spans, this is the rule to start with:
bugsnag_list_spans is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect SmartBear MCP, apply this rule, and every bugsnag_list_spans call is checked against it from then on.
Questions about bugsnag_list_spans
Get individual spans belonging to a span group 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. - spanGroupId (string) *required*: ID of the span group - sort (enum): Field to sort by - 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. - filters (record<string, array>): Apply filters to narrow down the span group list. Use the List Trace Fields 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: {"span.since":[{"type":"eq","value":"7d"}]}) Use Cases: 1. Analyze individual slow operations 2. Debug performance issues by examining specific traces 3. Find patterns in operation attributes Examples: 1. Get slowest spans for an operation json { "spanGroupId": "[HttpClient]GET-api.example.com", "sort": "duration", "direction": "desc", "perPage": 10 } Expected Output: Array of the 10 slowest span instances 2. Get spans filtered by OS with pagination json { "spanGroupId": "[HttpClient]GET-api.example.com", "sort": "timestamp", "filters": { "os.name": [ { "type": "eq", "value": "iOS" } ] }, "nextUrl": "/projects/123/spans?offset=30&per_page=30" } Expected Output: Array of spans from iOS devices with next page navigation Hints: 1. Sort by duration descending to find the slowest instances 2. Each span includes trace ID for further investigation. It is categorised as a Read tool in the SmartBear MCP MCP Server, which means it retrieves data without modifying state.
bugsnag_list_spans accepts 7 parameters: sort, filters, nextUrl, perPage, direction, projectId, spanGroupId. Required: spanGroupId. 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_spans: 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_spans 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_spans 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_spans. 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_spans 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.
More on SmartBear, and thousands of servers like it.
This server
Across the catalogue