debug_getCallStack

THE RISK

Low Risk

Why debug_getCallStack needs a policy

This tool retrieves debugging information (call stack/stack trace) from an already-paused debug session. It has no side effects, does not execute code, does not modify state, and does not delete data. It is purely informational. While it operates within a debugging context, the specific action is to read and display execution flow information, placing it in the Read category.

From the tool's definition Tool name 'debug_getCallStack' and description 'Get the current call stack/stack trace from the paused debug session' indicate a retrieval operation that queries the current state of the debugger without modifying, executing, or deleting anything.

Documented attack patterns abuse exactly the kind of access debug_getCallStack gives an agent:

POLICY

How to control debug_getCallStack

PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Server for VS Code, and nothing reaches the server without passing your rules. This is the rule we recommend for debug_getCallStack:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "debug_getCallStack": {}
  }
}

debug_getCallStack is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register MCP Server for VS Code — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More MCP Server for VS Code tools

Destructive debug_clearBreakpoints Remove all breakpoints from the workspace Execute debug_evaluateExpression Evaluate an expression in the current debug context (REPL/watch functionality). Test hypot Execute debug_startSession Start a debug session using a configuration from launch.json. Launch debugging instantly - Execute debug_stepOver Step over the current line of code (execute current line without entering functions) Execute debug_stopSession Stop the current debug session Execute debug_continueExecution Continue execution from the current breakpoint or paused state Execute debug_pauseExecution Pause the running debug session at the current execution point Execute debug_stepInto Step into function calls on the current line

All 25 MCP Server for VS Code tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about debug_getCallStack

What does the debug_getCallStack tool do? +

Get the current call stack/stack trace from the paused debug session. Understand execution flow instantly - see the complete call chain at a glance. It is categorised as a Read tool in the MCP Server for VS Code MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on debug_getCallStack? +

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

What risk level is debug_getCallStack? +

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

Can I rate-limit debug_getCallStack? +

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

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

debug_getCallStack is provided by the MCP Server for VS Code MCP server (malvex/mcp-server-vscode). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every MCP Server for VS Code tool call.

Start from MCP Server for VS Code, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →