bugsnag_get_release

SERVERSmartBear MCP SOURCESmartBear/smartbear-mcp

Low RISK CLASS

Category Read

Parameters 21 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/smartbear-mcp/bugsnag-get-release.md

WHAT IT DOES

What bugsnag_get_release does on SmartBear MCP

AI agents call bugsnag_get_release 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
`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.
`releaseId`	string	Yes	Unique identifier of the app release

Parameters from the server's own tool schema.

RISK

Why bugsnag_get_release is rated Low

This tool retrieves and displays metadata about a software release, including version information, source control details, and stability metrics. It has no side effects—it only queries and returns existing data. No code execution, data modification, deletion, or financial operations are involved. This is a straightforward read operation with minimal blast radius if misused by an AI agent.

From the tool's definition Tool name 'bugsnag_get_release' and description 'Get more details for a specific release' indicate a retrieval operation. Parameters are read-only identifiers (projectId, releaseId).

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs bugsnag_get_release 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_release, this is the rule to start with:

bugsnag_get_release Allowed

bugsnag_get_release is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "bugsnag_get_release": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect SmartBear MCP, apply this rule, and every bugsnag_get_release call is checked against it from then on.

FAQ

Questions about bugsnag_get_release

What does the bugsnag_get_release tool do? +

Get more details for a specific release by its ID, including source control information and associated builds 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. - releaseId (string) *required*: Unique identifier of the app release Output Description: JSON object containing release details along with stability metrics such as user and session stability, and whether it meets project targets Use Cases: 1. View release metadata such as version, source control info, and error counts 2. Analyze the stability data and targets for a release 3. See the builds that make up the release Examples: 1. Get details for a specific release json { "releaseId": "5f8d0d55c9e77c0017a1b2c3" } Expected Output: JSON object with release details including version, source control info, error counts and stability data. Hints: 1. Release IDs can be found using the List releases tool. It is categorised as a Read tool in the SmartBear MCP MCP Server, which means it retrieves data without modifying state.

What parameters does bugsnag_get_release accept? +

bugsnag_get_release accepts 2 parameters: projectId, releaseId. Required: releaseId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on bugsnag_get_release? +

Register the SmartBear MCP server in PolicyLayer and add a rule for bugsnag_get_release: 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.

What risk level is bugsnag_get_release? +

bugsnag_get_release is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit bugsnag_get_release? +

Yes. Add a rate_limit block to the bugsnag_get_release 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.

How do I block bugsnag_get_release completely? +

Set action: deny in the PolicyLayer policy for bugsnag_get_release. 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.

What MCP server provides bugsnag_get_release? +

bugsnag_get_release 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.

KEEP EXPLORING

More on SmartBear, and thousands of servers like it.

This server

All 240 SmartBear tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →