debugger_get_call_stack

Get the current call stack when paused (with function names, URLs, line numbers)

Server CDP-MCP Server jekyll-001/cdp-mcp-server
Category Read
Risk class Low
Parameters 00 required

What debugger_get_call_stack does on CDP-MCP Server

AI agents call debugger_get_call_stack to retrieve information from CDP-MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why debugger_get_call_stack needs a policy

This tool only queries and returns debugger information about the current execution state. It does not modify any data, execute code, trigger external actions, or cause irreversible changes. The low severity reflects that exposing call stack information to an AI agent poses minimal risk — the agent can learn about code execution flow but cannot manipulate it directly through this tool alone.

From the tool's definition Tool description states 'Get the current call stack when paused' — this is a read-only retrieval of debugger state information (function names, URLs, line numbers) with no side effects on the browser or its data.

Questions about debugger_get_call_stack

What does the debugger_get_call_stack tool do? +

Get the current call stack when paused (with function names, URLs, line numbers). It is categorised as a Read tool in the CDP-MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on debugger_get_call_stack? +

Register the CDP-MCP Server MCP server in PolicyLayer and add a rule for debugger_get_call_stack: 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 CDP-MCP Server. Nothing to install.

What risk level is debugger_get_call_stack? +

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

Can I rate-limit debugger_get_call_stack? +

Yes. Add a rate_limit block to the debugger_get_call_stack 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 debugger_get_call_stack completely? +

Set action: deny in the PolicyLayer policy for debugger_get_call_stack. 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 debugger_get_call_stack? +

debugger_get_call_stack is provided by the CDP-MCP Server MCP server (jekyll-001/cdp-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.