bugsnag_get_span_group
Get detailed performance metrics for a specific 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 - filters (...
This record as markdown: /tools/smartbear-mcp/bugsnag-get-span-group.md
What bugsnag_get_span_group does on SmartBear MCP
AI agents call bugsnag_get_span_group 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 |
|---|---|---|---|
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 |
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_get_span_group is rated Low
This is a retrieval operation that queries performance metrics from BugSnag without any side effects. It follows the Read category pattern: fetches existing observability data based on identifiers and filters. No data is created, modified, deleted, or executed.
From the tool's definition Tool name contains 'get' and description states 'Get detailed performance metrics for a specific span group'. Parameters are for querying/filtering existing data (projectId, spanGroupId, filters) with no modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
The rule that runs bugsnag_get_span_group 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_get_span_group, this is the rule to start with:
bugsnag_get_span_group 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_get_span_group call is checked against it from then on.
Questions about bugsnag_get_span_group
Get detailed performance metrics for a specific 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 - 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. View detailed statistics (p50, p75, p90, p95, p99) for an operation 2. Check if performance targets are configured 3. Monitor span count to understand operation volume Examples: 1. Get details for an API endpoint span group json { "spanGroupId": "[HttpClient]GET-api.example.com" } Expected Output: Statistics, category, and performance target info 2. Get span group details with device filtering json { "spanGroupId": "[HttpClient]GET-api.example.com", "filters": { "device.browser_name": [ { "type": "eq", "value": "Chrome" } ] } } Expected Output: Statistics filtered for Chrome browser only Hints: 1. Use List Span Groups first to discover available span group IDs 2. IDs are automatically URL-encoded - provide the raw ID 3. Statistics include p50, p75, p90, p95, p99 percentiles. It is categorised as a Read tool in the SmartBear MCP MCP Server, which means it retrieves data without modifying state.
bugsnag_get_span_group accepts 3 parameters: filters, 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_get_span_group: 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_get_span_group 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_get_span_group 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_get_span_group. 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_get_span_group 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