dbg_stack_trace

Return the current call stack. Requires a stop; a running program is refused (not_stopped) rather than answered with the empty frame list it used to return.

SERVERBreakpoint SOURCEbreakpoint-mcp

Low RISK CLASS

Category Read

Parameters 10 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/breakpoint-mcp/dbg-stack-trace.md

WHAT IT DOES

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.

RISK

Why dbg_stack_trace is rated Low

Even though dbg_stack_trace only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

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 Allowed

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

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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.

FAQ

Questions about dbg_stack_trace

What does the dbg_stack_trace tool do? +

Return the current call stack. Requires a stop; a running program is refused (not_stopped) rather than answered with the empty frame list it used to return. It is categorised as a Read tool in the Breakpoint MCP Server, which means it retrieves data without modifying state.

What parameters does dbg_stack_trace accept? +

dbg_stack_trace accepts 1 parameter: levels. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on dbg_stack_trace? +

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.

What risk level is dbg_stack_trace? +

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

Can I rate-limit dbg_stack_trace? +

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.

How do I block dbg_stack_trace completely? +

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.

What MCP server provides dbg_stack_trace? +

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.

KEEP EXPLORING

More on Breakpoint, and thousands of servers like it.

This server

All 280 Breakpoint tools →

Across the catalogue

The MCP Attack Database →

Guides

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