Get current call stack (DAP standard name)
AI agents call stackTrace to retrieve information from MCP Chrome Debugger Protocol without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The stackTrace tool retrieves the current call stack from a Node.js process being debugged. This is a passive information-gathering operation. It does not execute code, modify state, delete data, or move money. While it provides visibility into a running process, the act of reading the stack trace itself has no side effects or blast radius beyond information disclosure.
From the tool's definition Tool is named 'stackTrace' and described as 'Get current call stack (DAP standard name)'. This is a read-only operation that retrieves debugging information about the execution state without modifying any data or triggering side effects.
Attacks that exploit this kind of access
Get current call stack (DAP standard name). It is categorised as a Read tool in the MCP Chrome Debugger Protocol MCP Server, which means it retrieves data without modifying state.
Register the MCP Chrome Debugger Protocol MCP server in PolicyLayer and add a rule for 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 MCP Chrome Debugger Protocol. Nothing to install.
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 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 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.
stackTrace is provided by the MCP Chrome Debugger Protocol MCP server (vitalyostanin/mcp-chrome-debugger-protocol). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →