bugsnag_get_trace
Get all spans within a specific trace 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. - traceId (string) *required*: Trace ID - from (string) *required*: Start time (ISO 8601...
This record as markdown: /tools/smartbear-mcp/bugsnag-get-trace.md
What bugsnag_get_trace does on SmartBear MCP
AI agents call bugsnag_get_trace 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 |
|---|---|---|---|
to | string | Yes | End time (ISO 8601 format) |
from | string | Yes | Start time (ISO 8601 format) |
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. |
traceId | string | Yes | Trace ID |
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. |
targetSpanId | string | — | Optional target span ID to focus on |
Parameters from the server's own tool schema.
Why bugsnag_get_trace is rated Low
This tool retrieves observability/tracing data from BugSnag without creating, modifying, or deleting any resources. It is a straightforward data query operation. The blast radius is minimal—unauthorized access to trace data could leak application performance or debugging information, but cannot damage systems or trigger unwanted side effects.
From the tool's definition Tool description: 'Get all spans within a specific trace' — retrieves trace and span data from BugSnag. Parameters are all query/filter inputs (projectId, traceId, from, to, targetSpanId, perPage, nextUrl) with no modification or deletion capabilities.
Attacks that exploit this kind of access
The rule that runs bugsnag_get_trace 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_trace, this is the rule to start with:
bugsnag_get_trace 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_trace call is checked against it from then on.
Questions about bugsnag_get_trace
Get all spans within a specific trace 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. - traceId (string) *required*: Trace ID - from (string) *required*: Start time (ISO 8601 format) - to (string) *required*: End time (ISO 8601 format) - targetSpanId (string): Optional target span ID to focus on - 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. Use Cases: 1. Debug slow requests by viewing all operations in the trace 2. Understand the flow of a request through the system 3. Identify bottlenecks in distributed systems Examples: 1. Get all spans for a trace json { "traceId": "abc123", "from": "2024-01-01T00:00:00Z", "to": "2024-01-01T23:59:59Z" } Expected Output: Array of all spans in the trace with timing and hierarchy 2. Get spans for a trace with pagination and target span json { "traceId": "def456", "from": "2024-01-01T00:00:00Z", "to": "2024-01-01T23:59:59Z", "targetSpanId": "span-789", "perPage": 50 } Expected Output: Array of up to 50 spans focused around the target span Hints: 1. Traces show the complete execution path of a request 2. Use from/to parameters to narrow the time window 3. targetSpanId can be used to focus on a specific span in the trace. It is categorised as a Read tool in the SmartBear MCP MCP Server, which means it retrieves data without modifying state.
bugsnag_get_trace accepts 7 parameters: to, from, nextUrl, perPage, traceId, projectId, targetSpanId. Required: to, from, traceId. 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_trace: 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_trace 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_trace 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_trace. 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_trace 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