dbg_stack_trace
Return the current call stack (only meaningful while stopped at a breakpoint).
This record as markdown: /tools/breakpoint-mcp/dbg-stack-trace.md
What dbg_stack_trace does on Breakpoint
AI agents call dbg_stack_trace to retrieve information from Breakpoint 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 |
|---|---|---|---|
levels | integer | — | Max frames (default 20) |
Parameters from the server's own tool schema.
Why dbg_stack_trace is rated Low
This tool reads and returns debug state information (the call stack) without modifying anything. It is a pure read/query operation with minimal blast radius.
From the tool's definition Return the current call stack (only meaningful while stopped at a breakpoint)
Attacks that exploit this kind of access
The rule that runs dbg_stack_trace safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Breakpoint, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For dbg_stack_trace, this is the rule to start with:
dbg_stack_trace 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 Breakpoint, apply this rule, and every dbg_stack_trace call is checked against it from then on.
Questions about dbg_stack_trace
Return the current call stack (only meaningful while stopped at a breakpoint). It is categorised as a Read tool in the Breakpoint MCP Server, which means it retrieves data without modifying state.
dbg_stack_trace accepts 1 parameter: levels. The full parameter table on this page comes from the server's own tool schema.
Register the Breakpoint MCP server in PolicyLayer and add a rule for dbg_stack_trace: 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 Breakpoint. Nothing to install.
dbg_stack_trace 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 dbg_stack_trace 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 dbg_stack_trace. 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.
dbg_stack_trace is provided by the Breakpoint MCP server (breakpoint-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Breakpoint, and thousands of servers like it.
This server
Across the catalogue