Extract and format stacktrace information from an event
AI agents call view_stacktrace 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 stacktrace information from an already-occurring error event in Bugsnag. It performs data extraction and formatting only, with no capability to modify, delete, or execute operations. The context (investigating errors via natural language) further supports this as a read-only diagnostic tool. Blast radius is minimal as misuse would only expose technical debugging information already in the system.
From the tool's definition Tool name is 'view_stacktrace' and description states 'Extract and format stacktrace information from an event' — purely retrieves and displays existing data with no modifications, deletions, or side effects.
Documented attack patterns abuse exactly the kind of access view_stacktrace 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_stacktrace:
{
"version": "1",
"default": "deny",
"tools": {
"view_stacktrace": {}
}
}view_stacktrace 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.
Extract and format stacktrace information from an event. 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_stacktrace: 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_stacktrace 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_stacktrace 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_stacktrace. 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_stacktrace 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.