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

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

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

Questions about bugsnag_get_event

What does the bugsnag_get_event tool do? +

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.

What parameters does bugsnag_get_event accept? +

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.

How do I enforce a policy on bugsnag_get_event? +

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.

What risk level is bugsnag_get_event? +

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

Can I rate-limit bugsnag_get_event? +

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.

How do I block bugsnag_get_event completely? +

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.

What MCP server provides bugsnag_get_event? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of SmartBear's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.