bugsnag_get_event
Get detailed information about a specific event 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. - eventId (string) *required*: Unique identifier of the event Use Cases: 1. Ge...
This record as markdown: /tools/smartbear-mcp/bugsnag-get-event.md
What bugsnag_get_event does on SmartBear MCP
AI agents call bugsnag_get_event 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 |
|---|---|---|---|
eventId | string | Yes | Unique identifier of the event |
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. |
Parameters from the server's own tool schema.
Why bugsnag_get_event is rated Low
This tool performs a query/retrieval operation against the BugSnag error tracking system. It fetches and returns event data without modifying, deleting, or executing any operations. The blast radius is minimal—an agent could retrieve sensitive error information but cannot alter data or trigger external actions.
From the tool's definition Tool retrieves "detailed information about a specific event" and returns "JSON object with complete event details including stack trace". The parameters are read-only identifiers (projectId, eventId) with no mutation or deletion capability.
Attacks that exploit this kind of access
The rule that runs bugsnag_get_event 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_event, this is the rule to start with:
bugsnag_get_event 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_event call is checked against it from then on.
Questions about bugsnag_get_event
Get detailed information about a specific event 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. - eventId (string) *required*: Unique identifier of the event Use Cases: 1. Get the full details of an event, including any thread stack traces Examples: 1. Get event details of an event json { "eventId": "6863e2af012caf1d5c320000" } Expected Output: JSON object with complete event details including stack trace (error trace and other threads, if present), metadata, and context. It is categorised as a Read tool in the SmartBear MCP MCP Server, which means it retrieves data without modifying state.
bugsnag_get_event accepts 2 parameters: eventId, projectId. Required: eventId. 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_event: 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_event 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_event 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_event. 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_event 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