bugsnag_list_releases
List releases for a project 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. - releaseStage (string): Filter releases by this stage (e.g. production, staging), defaults to 'pr...
This record as markdown: /tools/smartbear-mcp/bugsnag-list-releases.md
What bugsnag_list_releases does on SmartBear MCP
AI agents call bugsnag_list_releases 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 |
|---|---|---|---|
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. |
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. |
visibleOnly | boolean | — | Whether to only include releases that are marked as visible in the dashboard |
releaseStage | string | — | Filter releases by this stage (e.g. production, staging), defaults to 'production' |
Parameters from the server's own tool schema.
Why bugsnag_list_releases is rated Low
This tool retrieves and queries release data from BugSnag with optional filtering and pagination. It has no side effects—it neither creates, modifies, deletes, executes code, nor moves money. It is a straightforward read operation that presents no meaningful blast radius if misused by an AI agent.
From the tool's definition Tool name is 'bugsnag_list_releases' and description states 'List releases for a project'. Parameters include filters (releaseStage, visibleOnly, perPage) and pagination (nextUrl) but no mutation operations. All operations are query/retrieval based.
Attacks that exploit this kind of access
The rule that runs bugsnag_list_releases 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_releases, this is the rule to start with:
bugsnag_list_releases 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_releases call is checked against it from then on.
Questions about bugsnag_list_releases
List releases for a project 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. - releaseStage (string): Filter releases by this stage (e.g. production, staging), defaults to 'production' (default: "production") - visibleOnly (boolean): Whether to only include releases that are marked as visible in the dashboard (default: false) - 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. Output Description: JSON array of release summary objects with metadata, with a URL to the next page if more results are available Use Cases: 1. View recent releases to correlate with error spikes 2. Filter releases by stage (e.g. production, staging) for targeted analysis Examples: 1. List production releases for a project json {} Expected Output: JSON array of release objects in the production stage 2. List staging releases for a project json { "releaseStage": "staging" } Expected Output: JSON array of release objects in the staging stage 3. Get the next page of results json { "nextUrl": "/projects/515fb9337c1074f6fd000003/releases?offset=30&per_page=30" } Expected Output: JSON array of release objects with metadata from the next page Hints: 1. Use the Get Release tool to get more details on a specific release, including the builds it contains 2. The release stage defaults to 'production' if not specified 3. Use visibleOnly to filter out releases that have been marked as hidden in the dashboard. It is categorised as a Read tool in the SmartBear MCP MCP Server, which means it retrieves data without modifying state.
bugsnag_list_releases accepts 5 parameters: nextUrl, perPage, projectId, visibleOnly, releaseStage. 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_releases: 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_releases 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_releases 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_releases. 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_releases 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