View all event data tabs including app, device, user, request, breadcrumbs, metadata, and stacktrace
AI agents call view_tabs to retrieve information from Bugsnag MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays event diagnostic data for error investigation without any write, delete, or execute capabilities. The 'view' operation is inherently read-only. Even if exposed to an AI agent, the worst case is unauthorized information disclosure of error event data, which is low severity in a typical Bugsnag context where such access is expected during error investigation workflows.
From the tool's definition Tool description states 'View all event data tabs' - the verb 'View' indicates read-only retrieval of event data (app, device, user, request, breadcrumbs, metadata, stacktrace). No modification, deletion, or execution capabilities mentioned.
Documented attack patterns abuse exactly the kind of access view_tabs gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Bugsnag MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for view_tabs:
{
"version": "1",
"default": "deny",
"tools": {
"view_tabs": {}
}
}view_tabs is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
View all event data tabs including app, device, user, request, breadcrumbs, metadata, and stacktrace. It is categorised as a Read tool in the Bugsnag MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Bugsnag MCP Server MCP server in PolicyLayer and add a rule for view_tabs: 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 Bugsnag MCP Server. Nothing to install.
view_tabs 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 view_tabs 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 view_tabs. 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.
view_tabs is provided by the Bugsnag MCP Server MCP server (tgeselle/bugsnag-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Bugsnag MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
11 Bugsnag MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.