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...
Single-target operation
Part of the SmartBear MCP MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call bugsnag_get_trace to retrieve information from SmartBear MCP without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though bugsnag_get_trace only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
tools:
bugsnag_get_trace:
rules:
- action: allowSee the full SmartBear MCP policy for all 147 tools.
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.
Add a rule in your Intercept YAML policy under the tools section for bugsnag_get_trace. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the SmartBear MCP MCP server.
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 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_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 MCP server (@smartbear/mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept