Get more details for a specific build by its ID **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. - buildId (string) *required*: Unique identifier of the app build **Outp...
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_build 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_build 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_build:
rules:
- action: allowSee the full SmartBear MCP policy for all 147 tools.
Get more details for a specific build by its ID **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. - buildId (string) *required*: Unique identifier of the app build **Output Description:** JSON object containing build details along with stability metrics such as user and session stability, and whether it meets project targets **Use Cases:** 1. View build metadata such as version, source control info, and error counts 2. Analyze a specific build to correlate with error spikes or deployments 3. See the stability targets for a project and if the build meets them **Examples:** 1. Get details for a specific build ```json { "buildId": "5f8d0d55c9e77c0017a1b2c3" } ``` Expected Output: JSON object with build details including version, source control info, error counts and stability data. **Hints:** 1. Build IDs can be found using the List builds tool. 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_build. 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_build 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_build 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_build. 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_build 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