bugsnag_get_event_details_from_dashboard_url

SERVERSmartBear MCP SOURCESmartBear/smartbear-mcp

Low RISK CLASS

Category Read

Parameters 11 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-details-from-dashboard-url.md

WHAT IT DOES

What bugsnag_get_event_details_from_dashboard_url does on SmartBear MCP

AI agents call bugsnag_get_event_details_from_dashboard_url 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
`link`	string	Yes	Full URL to the event details page in the BugSnag dashboard (web interface), containing project slug and event_id parameter.

Parameters from the server's own tool schema.

RISK

Why bugsnag_get_event_details_from_dashboard_url is rated Low

This is a read-only operation that queries and retrieves existing event data from BugSnag's error tracking system. It takes a URL parameter and returns event details without creating, modifying, or deleting any data. The blast radius of misuse is minimal—an attacker could enumerate or access error details from shared or accessible URLs, but cannot alter system state or execute arbitrary code.

From the tool's definition Tool retrieves detailed information about a specific event using a dashboard URL. Description states 'Get detailed information about a specific event' and use cases include 'lookup of event details' and 'extract event information from shared links'.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

bugsnag_get_event_details_from_dashboard_url Allowed

bugsnag_get_event_details_from_dashboard_url 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_event_details_from_dashboard_url": {}
  }
}

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_event_details_from_dashboard_url call is checked against it from then on.

FAQ

Questions about bugsnag_get_event_details_from_dashboard_url

What does the bugsnag_get_event_details_from_dashboard_url tool do? +

Get detailed information about a specific event using its dashboard URL Parameters: - link (string) *required*: Full URL to the event details page in the BugSnag dashboard (web interface), containing project slug and event_id parameter. Use Cases: 1. Get event details when given a dashboard URL from a user or notification 2. Extract event information from shared links or browser URLs 3. Quick lookup of event details without needing separate project and event IDs Examples: 1. Get event details from a dashboard URL json { "link": "https://app.bugsnag.com/my-org/my-project/errors/6863e2af8c857c0a5023b411?event_id=6863e2af012caf1d5c320000" } Expected Output: JSON object with complete event details including stack trace, metadata, and context Hints: 1. The URL must contain both project slug in the path and event_id in query parameters 2. This is useful when users share BugSnag dashboard URLs and you need to extract the event data. 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_details_from_dashboard_url accept? +

bugsnag_get_event_details_from_dashboard_url accepts 1 parameter: link. Required: link. 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_details_from_dashboard_url? +

Register the SmartBear MCP server in PolicyLayer and add a rule for bugsnag_get_event_details_from_dashboard_url: 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_details_from_dashboard_url? +

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

Can I rate-limit bugsnag_get_event_details_from_dashboard_url? +

Yes. Add a rate_limit block to the bugsnag_get_event_details_from_dashboard_url 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_details_from_dashboard_url completely? +

Set action: deny in the PolicyLayer policy for bugsnag_get_event_details_from_dashboard_url. 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_details_from_dashboard_url? +

bugsnag_get_event_details_from_dashboard_url 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_event_details on CTFtime MCP Server →get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server → The MCP Attack Database →

Guides

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